Networked microphone devices, systems, and methods of localized arbitration

ABSTRACT

A first playback device is configured to perform functions comprising: detecting sound, identifying a wake word based on the sound as detected by the first device, receiving an indication that a second playback device has also detected the sound and identified the wake word based on the sound as detected by the second device, after receiving the indication, evaluating which of the first and second devices is to extract sound data representing the sound and thereby determining that the extraction of the sound data is to be performed by the second device over the first device, in response to the determining, foregoing extraction of the sound data, receiving VAS response data that is indicative of a given VAS response corresponding to a given voice input identified in the sound data extracted by the second device, and based on the VAS response data, output the given VAS response.

TECHNICAL FIELD

The present technology relates to consumer goods and, more particularly,to methods, systems, products, features, services, and other elementsdirected to voice-assisted control of media playback systems or someaspect thereof.

BACKGROUND

Options for accessing and listening to digital audio in an out-loudsetting were limited until in 2003, when SONOS, Inc. filed for one ofits first patent applications, entitled “Method for Synchronizing AudioPlayback between Multiple Networked Devices,” and began offering a mediaplayback system for sale in 2005. The SONOS Wireless HiFi System enablespeople to experience music from many sources via one or more networkedplayback devices. Through a software control application installed on asmartphone, tablet, or computer, one can play what he or she wants inany room that has a networked playback device. Additionally, using acontroller, for example, different songs can be streamed to each roomthat has a playback device, rooms can be grouped together forsynchronous playback, or the same song can be heard in all roomssynchronously.

Given the ever-growing interest in digital media, there continues to bea need to develop consumer-accessible technologies to further enhancethe listening experience.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1A is a partial cutaway view of an environment having a mediaplayback system configured in accordance with aspects of the disclosedtechnology.

FIG. 1B is a schematic diagram of the media playback system of FIG. 1Aand one or more networks;

FIG. 2A is a functional block diagram of an example playback device;

FIG. 2B is an isometric diagram of an example playback device thatincludes a network microphone device;

FIGS. 3A-3E are diagrams showing example playback device configurationsin accordance with aspects of the disclosure;

FIG. 4A is a functional block diagram of an example controller device inaccordance with aspects of the disclosure;

FIGS. 4B and 4C are controller interfaces in accordance with aspects ofthe disclosure;

FIG. 5 is a functional block diagram of certain components of an examplenetwork microphone device in accordance with aspects of the disclosure;

FIG. 6 is a diagram of an example voice input in accordance with aspectsof the disclosure;

FIG. 7A is a conceptual diagram of an example network system configuredin accordance with aspects of this disclosure;

FIG. 7B is a conceptual diagram of an example network system configuredin accordance with aspects of this disclosure;

FIG. 8A is a message flow diagram for a network system configured toperform arbitration in accordance with aspects of the disclosure;

FIG. 8B is an example message flow diagram for a network systemconfigured to perform arbitration in accordance with aspects of thedisclosure;

FIG. 9A is a conceptual diagram of an example network system configuredin accordance with aspects of this disclosure;

FIG. 9B is an example message flow diagram for a network systemconfigured to perform arbitration in accordance with aspects of thedisclosure; and

FIG. 10 is a flow diagram of an example method for performing localarbitration and designating voice output playback in accordance withaspects of the disclosure.

The drawings are for purposes of illustrating example embodiments, butit should be understood that the inventions are not limited to thearrangements and instrumentality shown in the drawings. In the drawings,identical reference numbers identify at least generally similarelements. To facilitate the discussion of any particular element, themost significant digit or digits of any reference number refers to theFigure in which that element is first introduced. For example, element103 a is first introduced and discussed with reference to FIG. 1A.

DETAILED DESCRIPTION

I. Overview

Voice control can be beneficial in a “smart” home that includes smartappliances and devices that are connected to a communication network,such as wireless audio playback devices, illumination devices, andhome-automation devices (e.g., thermostats, door locks, etc.). A networkmicrophone device (NMD) may be used to control smart home devices. Invarious implementations described in greater detail below, an NMD may beimplemented to control a playback device (which may include anNMD-equipped playback device), such as to adjust volume, change playbackstate (e.g., pause/play), select a song, and/or perform myriad otheroperations.

An NMD is a networked computing device that typically includes anarrangement of microphones, such as a microphone array, that isconfigured to detect sounds present in the NMD's environment. Thedetected sound may include a person's speech mixed with background noise(e.g., music being output by a playback device or other ambient noise).In practice, an NMD typically filters detected sound to remove thebackground noise from the person's speech to facilitate identifyingwhether the speech contains a voice input indicative of voice control.If so, the NMD may take action based on such a voice input.

A voice input will typically include a wake word followed by anutterance comprising a user request. A wake word is typically apredetermined word or phrase used to “wake up” an NMD and cause it toinvoke a particular voice assistant service (“VAS”) to interpret theintent of the voice input. In practice, an NMD will typically transmitthe voice input, or at least a portion thereof (e.g., the utteranceportion), to the VAS corresponding to the particular wake word containedin the voice input. For example, a user might speak the wake word“Alexa” to invoke the AMAZON VAS, “Ok, Google” to invoke the GOOGLE VAS,“Hey, Siri” to invoke the APPLE VAS, or “Hey, Sonos” to invoke a VASoffered by SONOS, among other examples. In practice, a wake word mayalso be referred to as, for example, an activation-, trigger-,wakeup-word or -phrase, and may take the form of any suitable word,combination of words (e.g., a particular phrase), and/or some otheraudio cue.

An NMD often employs a wake-word engine, which is typically onboard theNMD, to identify whether sound detected by the NMD contains a voiceinput that includes a particular wake word. The wake-word engine may beconfigured to identify (i.e., “spot”) a particular wake word using oneor more identification algorithms. This wake-word identification processis commonly referred to as “keyword spotting.” In practice, to helpfacilitate keyword spotting, the NMD may buffer sound detected by amicrophone of the NMD and then use the wake-word engine to process thatbuffered sound to determine whether a wake word is present.

When a wake-word engine spots a wake word in detected sound, the NMD maydetermine that a wake-word event (i.e., a “wake-word trigger”) hasoccurred, which indicates that the NMD has detected sound that includesa potential voice input. The occurrence of the wake-word event typicallycauses the NMD to perform additional processes involving the detectedsound. In some implementations, these additional processes may includeoutputting an alert (e.g., an audible chime and/or a light indicator)indicating that a wake word has been identified and extractingdetected-sound data from a buffer, among other possible additionalprocesses. Extracting the detected sound may include reading out andpackaging a stream of the detected-sound data according to a particularformat and transmitting the packaged detected-sound data to anappropriate VAS for interpretation.

In turn, the VAS corresponding to the wake word that was identified bythe wake-word engine receives the transmitted sound data from the NMDover a communication network. A VAS traditionally takes the form of aremote service implemented using one or more cloud servers configured toprocess voice inputs (e.g., AMAZON's ALEXA, APPLE's SIRI, MICROSOFT'sCORTANA, GOOGLE'S ASSISTANT, etc.). In some instances, certaincomponents and functionality of the VAS may be distributed across localand remote devices. Additionally, or alternatively, a VAS may take theform of a local service implemented at an NMD or a media playback systemcomprising the NMD such that a voice input or certain types of voiceinput (e.g., rudimentary commands) are processed locally withoutintervention from a remote VAS.

In any case, when a VAS receives detected-sound data, the VAS willtypically process this data, which involves identifying the voice inputand determining an intent of words captured in the voice input. The VASmay then provide a response back to the NMD with some instructionaccording to the determined intent. Based on that instruction, the NMDmay cause one or more smart devices to perform an action.

In operation, the action that the VAS instructs the NMD to take based onidentifying a voice input can take a variety of forms. For example, theinstruction may take the form of VAS response data that is indicative ofa given VAS response corresponding to the voice input for the NMD toplay back. The VAS response may generally involve the NMD outputtingvarious types of audio and/or visual indications. For instance, a VASresponse may comprise playing back chimes, spoken words, audible tones,and/or various other forms of audio played back in response to a voiceinput. Some of these VAS responses may indicate whether the VAS and/orthe NMD will perform a given action (e.g., begin music playback, outputrequested information, etc.) specified by the voice utterance of thevoice input. VAS responses may take various other forms as well.

In some implementations, an NMD may form part of a system comprisingmultiple NMDs. Indeed, a growing number of environments today havemultiple NMDs. For instance, a household may include multipleNMD-equipped playback devices to fill more areas and/or rooms of a homewith music and/or to provide more areas with voice-enabled services.

In environments having multiple NMDs, some or all of the NMDs mayidentify a same wake word. For example, when multiple NMDs in a givenenvironment are configured to identify the same ALEXA wake word, andmore than one of the NMDs identify the same wake word, each identifyingNMD may trigger its respective internal voice capture components toextract detected-sound data for evaluation by a VAS. When more than oneNMD identifies a common wake word, a VAS, which may be located in thecloud, may typically determine which of the NMDs identified the wakeword with a highest confidence level. The VAS will then select a givenNMD that identified the wake word with the highest confidence level, andafter selecting the given NMD that identified the wake word with thehighest measure of confidence, may cause the selected NMD to take one ormore actions, which may take the form of one or more outputs, as someexamples.

The non-selected NMDs may enter an idle state after determining thatthey have not been selected to perform extraction of detected-sounddata. The selected NMD will also return to an idle state afterextracting detected-sound data and/or generating any outputs. Once anNMD enters and idle state, an NMD may remain in the idle state until theNMD identifies another wake word.

When a user speaks the same wake word a subsequent time, and more thanone NMD again identifies the same wake word, the VAS repeats the processof selecting a given one of the NMDs that identified the wake word withthe highest confidence level. The NMD selected for the next interactionmay be the previously-selected NMD if the previously-selected NMDidentified the wake word with the highest confidence level or may beanother NMD if an NMD other than the previously-selected NMD identifiedthe wake word with the highest confidence level. The process ofselecting a given NMD to extract sound-data that may contain a voiceinput from multiple NMDs that have identified a particular wake word maybe referred to herein as “arbitration.”

Typically, the NMD that the VAS designates to perform extraction as partof performing the arbitration process is also designated to output theVAS response and to take one or more actions instructed by the VAS, forexample to control audio playback, etc. However, there may be issuesthat arise from designating the same NMD that is selected to performextraction to also output the VAS response and/or to take one or moreinstructed actions. Namely, the NMD that the VAS ultimately designatesto perform extraction may not be the NMD that the user expected tooutput the VAS response or to take the one or more actions instructed bythe VAS.

For instance, an NMD located in a different room than the user mayidentify a wake word with a greater confidence level than an NMD locatedin the same room as the user. As an example, the NMD in the differentroom may identify the wake word with a greater confidence level than theNMD in the same room as the user due to the way sound is reflected andabsorbed by objects and surfaces in the two rooms. In any case, theselected NMD located in the different room may then output a VASresponse. However, the user may have expected the NMD located in thesame room to output the VAS response rather than the NMD located in thedifferent room.

When an NMD other than the one a user expects outputs a VAS response inresponse to an identified wake word, this unexpected VAS response maycause user frustration. For example, a user located in a living room ofa home may have wanted an NMD to take an action instructed by the VAS inthe form of playing back audio in the living room. However, due to theacoustics in the user's home, the NMD in the bedroom may identify aspoken wake word with a higher confidence level than the NMD in theliving room. As a result, the NMD in the bedroom may output a VASresponse and may begin playing back audio in the bedroom. As a result ofthe NMD located in the bedroom playing back audio, the user may haveuser may have walk to the bedroom to stop the audio playback by speakingor otherwise issuing a command to stop the bedroom NMD's playback.

In some cases, the particular NMD that generates an output in responseto identifying a wake word at a given time may appear to be arbitrarilychosen and may change seemingly without explanation, a phenomenonreferred to herein as “ping-ponging.” Indeed, the NMDs that output VASresponses and/or take one or more actions instructed by the VAS inresponse to voice multiple inputs may appear to ping pong from one NMDto another NMD, which is seemingly arbitrary and also disorientating toa user. As an example, a user may speak a first wake word followed by afirst voice input. In response to identifying the first wake word with ahighest confidence level and being selected by a VAS, a first NMD of twoor more NMDs may generate an output. Thereafter, the user who may belocated in the same location as when speaking the first wake word andvoice input, may speak a second wake word followed by a second voiceinput. In response to identifying the second wake word, a second NMD ofthe two or more NMDs may generate an output. Thus, the output generatedby the first and second NMDs ping-pong's due to the outputting NMDchanging between the first and second NMDs in response to successivelyidentified wake words.

In addition to occurring between NMDs located in different rooms,ping-ponging can also occur between NMDs situated in the same room. Forexample, in response to a user speaking a first wake word followed by avoice utterance, a first NMD located near the user on one side of a roommay identify the first wake word with a higher confidence level than asecond NMD located on another side of a room. In response to the firstNMD identifying the first wake word with the higher confidence level,the first NMD may output a VAS response. After the speaking the firstwake word, the user may then turn to face the second NMD across the roomand may speak a second wake word followed by a second voice utteranceexpecting the second NMD to identify the wake word with a higherconfidence level, only to have the first NMD again identify the firstwake word with a higher confidence level and respond to the user byoutputting a VAS response.

Additionally, in the implementations described above, each NMD thatidentifies a given wake word followed by a voice utterance may transmitdata associated with the voice utterance and/or wake word to the VAS,which is typically located in the cloud. The overall amount of bandwidthutilized by a media playback system having multiple NMDs that each senddata for arbitration do a cloud-based VAS may be relatively high giventhat each NMD sends data associated with a wake word and/or a voiceutterance to the VAS.

Example devices, systems, and methods disclosed herein address these andother technical problems that arise in the context of multiple NMDs.More specifically, this disclosure describes in various embodiments NMDsare configured to locally arbitrate between one another (i.e., ratherthan using remote cloud servers to perform arbitration). In one aspectof this disclosure, a single NMD within a set of NMDs is selected as thelocal arbitrator, or “arbitrator NMD.” Further, performing localarbitration as described herein may be advantageous over remotearbitration because of the bandwidth savings achieved by avoidingsending the data of multiple redundant wake words and/or voice inputsfrom each NMD to the VAS for remote arbitration. Local arbitration maybe advantageous for a variety of other reasons as well.

In a related aspect, the arbitrator NMD may also be designated foroutputting VAS responses, which may provide a behavior that more closelyaligns with a user's expectations and reduces or eliminates theaforementioned unexpected behaviors, such as ping-ponging. While thearbitrator NMD is described as being the same NMD that is designated foroutputting VAS responses, it should be understood that an NMD other thanthe arbitrator may be designated for outputting a VAS response as well.

In example embodiments, a network media playback system includes two ormore NMDs, each of which is configured to detect sound that may comprisea voice input. At least one of these NMDs may be designated as thearbitrator NMD, which may be responsible for selecting which NMD is tobe the default NMD for outputting a VAS response among a set of NMDsthat have identified a same wake word. In various embodiments, the localarbitrator may also determine the NMD among the set of NMDs that is toextract detected-sound data for evaluation by a VAS in response tomultiple NMDs in the set identifying a same wake word. In someembodiments, an NMD other than the arbitrator may be selected to extractdetected-sound data to a remote VAS.

In some implementations, a device that may be designated to output a VASresponse, which may comprise the arbitrator NMD, may be assigned duringthe configuration of the media playback system that includes the two ormore NMDs. In some cases, the arbitrator responsibilities may beassigned to a given NMD in the set based on the NMD's role or hardwareresources.

In addition, or alternatively, the arbitrator responsibilities may beassigned to a given NMD based on other considerations. For instance, thearbitrator responsibilities may be assigned to an NMD that has alreadybeen assigned other responsibilities within the media playback system.As one example, an NMD designated as the “group coordinator” that isresponsible for facilitating synchronous playback of audio among the twoor more NMDs may be assigned the arbitrator responsibilities as well. Asanother example, an NMD designated as the “primary” device that isresponsible for playing back a given audio channel, such as the centerchannel of a home theatre setup or either the left channel of a stereopair setup, may also be assigned the arbitrator responsibilities.However, in other instances, the arbitrator NMD may not be assigned anyof the aforementioned other responsibilities.

In any case, in accordance with example embodiments provided herein,local arbitration may generally involve two or more NMDs of the mediaplayback system identifying a particular wake word, the arbitrator NMDselecting one of the NMDs to extract detected-sound data that mayinclude a voice input for evaluation by the VAS, and after evaluation ofthe voice input by the VAS, the arbitrator NMD playing back a VASresponse generated by the VAS.

More specifically, in an example implementation, each non-arbitrator NMDthat identifies a particular wake word may transmit to the arbitratorNMD a notification that a wake word was identified. In some examples, agiven notification may include a confidence level that the givennon-arbitrator NMD identified the particular wake word correctly. In thecase that an identifying NMD is the arbitrator NMD, the arbitrator NMDmay not transmit a message that includes a confidence level but insteadmay generate an internal notification, which may include a confidencelevel that the arbitrator NMD identified the wake word correctly.

In practice, a confidence level may take various forms. For example, theconfidence level may be a metric calculated based on audio properties ofthe received wake word. Examples of some such metrics that may be usedto calculate the confidence level may include a signal-to-noise ratio(SnR), a frequency spectrum of the identified wake word, a direction ofthe identified wake word, an amplitude (e.g., decibel level) of theidentified wake word, etc. A confidence level may take various otherforms as well.

In turn, the arbitrator NMD receives each of the notifications. Based onthese notifications, the arbitrator NMD may determine that more than oneof the NMDs has identified the wake word at the same time. In responseto this determination, the arbitrator NMD may next select which of theidentifying NMDs is to extract the detected-sound data for evaluation bythe VAS. The arbitrator NMD may make this selection in various manners.

As one example, if the notifications include respective confidencelevels, the arbitrator NMD may select the NMD having the highestconfidence level. As another example, if the NMDs have differing roles,the arbitrator NMD may use these roles as a basis for selecting the NMD.Other examples of selecting the extraction NMD are also possible.

After selecting an NMD to extract the voice input, the arbitrator NMDmay cause the selected NMD to extract detected-sound data that mayinclude a voice input for evaluation by the VAS. In this respect, itshould be understood that the extraction NMD may differ from, or be thesame as, the arbitrator NMD that is designated to output a voice output.The process of causing the selected NMD to extract the detected-sounddata that may include a voice input may take various forms.

As one example, if the arbitrator NMD selects a non-arbitrator NMD, thenthe arbitrator NMD may send an instruction to the non-arbitrator NMD toextract the detected-sound data for evaluation by the appropriate VAS.As another example, if the arbitrator NMD selects itself, then thearbitrator NMD may trigger its internal voice capture components toextract the detected-sound data that may include a voice input forevaluation by the VAS.

After extracting the voice input, the selected NMD may format thedetected-sound data into a sound-data stream and transmit the sound-datastream containing at least the detected-sound data that may include avoice input (and perhaps also the wake word) to the VAS either directlyvia a communication network that couples the VAS and the media playbacksystem or indirectly via the arbitrator NMD. In this respect, only oneNMD transmits a sound-data stream to the VAS, which consumessignificantly less bandwidth than when multiple NMDs make suchtransmission.

Based on the received the sound-data stream, the VAS may identify avoice input comprising a voice utterance and may determine an intent ofthe voice utterance. In this regard, the VAS advantageously only has toprocess a sound-data stream from the media playback system and does notneed to perform analyses related to remote arbitration, which may helpto conserve the VAS's compute resources.

Thereafter, the VAS may determine the identity of the arbitrator NMD andsend to the arbitrator NMD a message including VAS response data that isindicative of a given VAS response via the communication network.

The VAS may determine the identity of the arbitrator of the NMD invarious different manners. According to an embodiment, the VAS mayidentify the arbitrator NMD via UPnP (Universal Plug 'n Play). As oneexample, UPnP eventing may be used to set the value of a state indicatorthat specifies the identity of the arbitrator NMD to the VAS. Inpractice, the group coordinator of a set of NMDs may be the arbitratorNMD. The VAS may determine the identity of the arbitrator NMD in variousother manners as well.

After receiving the VAS response data that is indicative of a given VASresponse, the arbitrator NMD outputs the VAS response. In this way, themedia playback system exhibits a more predictable behavior that alignswith users' expectations.

While some embodiments described herein may refer to functions performedby given actors, such as “users” and/or other entities, it should beunderstood that this description is for purposes of explanation only.The claims should not be interpreted to require action by any suchexample actor unless explicitly required by the language of the claimsthemselves.

II. Example Operating Environment

FIGS. 1A and 1B illustrate an example configuration of a media playbacksystem 100 (or “MPS 100”) in which one or more embodiments disclosedherein may be implemented. Referring first to FIG. 1A, the MPS 100 asshown is associated with an example home environment having a pluralityof rooms and spaces, which may be collectively referred to as a “homeenvironment,” “smart home,” or “environment 101.” The environment 101comprises a household having several rooms, spaces, and/or playbackzones, including a master bathroom 101 a, a master bedroom 101 b(referred to herein as “Nick's Room”), a second bedroom 101 c, a familyroom or den 101 d, an office 101 e, a living room 101 f, a dining room101 g, a kitchen 101 h, and an outdoor patio 101 i. While certainembodiments and examples are described below in the context of a homeenvironment, the technologies described herein may be implemented inother types of environments. In some embodiments, for example, the MPS100 can be implemented in one or more commercial settings (e.g., arestaurant, mall, airport, hotel, a retail or other store), one or morevehicles (e.g., a sports utility vehicle, bus, car, a ship, a boat, anairplane), multiple environments (e.g., a combination of home andvehicle environments), and/or another suitable environment wheremulti-zone audio may be desirable.

Within these rooms and spaces, the MPS 100 includes one or morecomputing devices. Referring to FIGS. 1A and 1B together, such computingdevices can include playback devices 102 (identified individually asplayback devices 102 a-102 o), network microphone devices 103(identified individually as “NMDs” 103 a-102 i), and controller devices104 a and 104 b (collectively “controller devices 104”). Referring toFIG. 1B, the home environment may include additional and/or othercomputing devices, including local network devices, such as one or moresmart illumination devices 108 (FIG. 1B), a smart thermostat 100, and alocal computing device 105 (FIG. 1A). In embodiments described below,one or more of the various playback devices 102 may be configured asportable playback devices, while others may be configured as stationaryplayback devices. For example, the headphones 102 o (FIG. 1B) are aportable playback device, while the playback device 102 d on thebookcase may be a stationary device. As another example, the playbackdevice 102 c on the patio may be a battery-powered device, which mayallow it to be transported to various areas within the environment 101,and outside of the environment 101, when it is not plugged in to a walloutlet or the like.

With reference still to FIG. 1B, the various playback, networkmicrophone, and controller devices 102-104 and/or other network devicesof the MPS 100 may be coupled to one another via point-to-pointconnections and/or over other connections, which may be wired and/orwireless, via a LAN 101 including a network router 109. For example, theplayback device 102 j in the Den 101 d (FIG. 1A), which may bedesignated as the “Left” device, may have a point-to-point connectionwith the playback device 102 a, which is also in the Den 101 d and maybe designated as the “Right” device. In a related embodiment, the Leftplayback device 102 j may communicate with other network devices, suchas the playback device 102 b, which may be designated as the “Front”device, via a point-to-point connection and/or other connections via theLAN 101.

As further shown in FIG. 1B, the MPS 100 may be coupled to one or moreremote computing devices 106 via a wide area network (“WAN”) 107. Insome embodiments, each remote computing device 106 may take the form ofone or more cloud servers. The remote computing devices 106 may beconfigured to interact with computing devices in the environment 101 invarious ways. For example, the remote computing devices 106 may beconfigured to facilitate streaming and/or controlling playback of mediacontent, such as audio, in the home environment 101.

In some implementations, the various playback devices, NMDs, and/orcontroller devices 102-104 may be communicatively coupled to at leastone remote computing device associated with a VAS and at least oneremote computing device associated with a media content service (“MCS”).For instance, in the illustrated example of FIG. 1B, remote computingdevices 106 a are associated with a VAS 190 and remote computing devices106 b are associated with an MCS 192. Although only a single VAS 190 anda single MCS 192 are shown in the example of FIG. 1B for purposes ofclarity, the MPS 100 may be coupled to multiple, different VASes and/orMCSes. In some implementations, VASes may be operated by one or more ofAMAZON, GOOGLE, APPLE, MICROSOFT, SONOS or other voice assistantproviders. In some implementations, MCSes may be operated by one or moreof SPOTIFY, PANDORA, AMAZON MUSIC, or other media content services.

As further shown in FIG. 1B, the remote computing devices 106 furtherinclude remote computing device 106 c configured to perform certainoperations, such as remotely facilitating media playback functions,managing device and system status information, directing communicationsbetween the devices of the MPS 100 and one or multiple VASes and/orMCSes, among other operations. In one example, the remote computingdevices 106 c provide cloud servers for one or more SONOS Wireless HiFiSystems.

In various implementations, one or more of the playback devices 102 maytake the form of or include an on-board (e.g., integrated) networkmicrophone device. For example, the playback devices 102 a-e include orare otherwise equipped with corresponding NMDs 103 a-e, respectively. Aplayback device that includes or is equipped with an NMD may be referredto herein interchangeably as a playback device or an NMD unlessindicated otherwise in the description.

In some cases, one or more of the NMDs 103 may be a stand-alone device.For example, the NMDs 103 f and 103 g may be stand-alone devices. Astand-alone NMD may omit components and/or functionality that istypically included in a playback device, such as a speaker or relatedelectronics. For instance, in such cases, a stand-alone NMD may notproduce audio output or may produce limited audio output (e.g.,relatively low-quality audio output).

The various playback and network microphone devices 102 and 103 of theMPS 100 may each be associated with a unique name, which may be assignedto the respective devices by a user, such as during setup of one or moreof these devices. For instance, as shown in the illustrated example ofFIG. 1B, a user may assign the name “Bookcase” to playback device 102 dbecause it is physically situated on a bookcase. Similarly, the NMD 103f may be assigned the named “Island” because it is physically situatedon an island countertop in the Kitchen 101 h (FIG. 1A). Some playbackdevices may be assigned names according to a zone or room, such as theplayback devices 102 e, 102 l, 102 m, and 102 n, which are named“Bedroom,” “Dining Room,” “Living Room,” and “Office,” respectively.Further, certain playback devices may have functionally descriptivenames. For example, the playback devices 102 a and 102 b are assignedthe names “Right” and “Front,” respectively, because these two devicesare configured to provide specific audio channels during media playbackin the zone of the Den 101 d (FIG. 1A). The playback device 102 c in thePatio may be named portable because it is battery-powered and/or readilytransportable to different areas of the environment 101. Other namingconventions are possible.

As discussed above, an NMD may detect and process sound from itsenvironment, such as sound that includes background noise mixed withspeech spoken by a person in the NMD's vicinity. For example, as soundsare detected by the NMD in the environment, the NMD may process thedetected sound to determine if the sound includes speech that containsvoice input intended for the NMD and ultimately a particular VAS. Forexample, the NMD may identify whether speech includes a wake wordassociated with a particular VAS.

In the illustrated example of FIG. 1B, the NMDs 103 are configured tointeract with the VAS 190 over a network via the LAN 101 and the router109. Interactions with the VAS 190 may be initiated, for example, whenan NMD identifies in the detected sound a potential wake word. Theidentification causes a wake-word event, which in turn causes the NMD tobegin transmitting detected-sound data to the VAS 190. In someimplementations, the various local network devices 102-105 (FIG. 1A)and/or remote computing devices 106 c of the MPS 100 may exchangevarious feedback, information, instructions, and/or related data withthe remote computing devices associated with the selected VAS. Suchexchanges may be related to or independent of transmitted messagescontaining voice inputs. In some embodiments, the remote computingdevice(s) and the media playback system 100 may exchange data viacommunication paths as described herein and/or using a metadata exchangechannel as described in U.S. application Ser. No. 15/438,749 filed Feb.21, 2017, and titled “Voice Control of a Media Playback System,” whichis herein incorporated by reference in its entirety.

Upon receiving the stream of sound data, the VAS 190 determines if thereis voice input in the streamed data from the NMD, and if so the VAS 190will also determine an underlying intent in the voice input. The VAS 190may next transmit a response back to the MPS 100, which can includetransmitting the response directly to the NMD that caused the wake-wordevent. The response is typically based on the intent that the VAS 190determined was present in the voice input. As an example, in response tothe VAS 190 receiving a voice input with an utterance to “Play Hey Judeby The Beatles,” the VAS 190 may determine that the underlying intent ofthe voice input is to initiate playback and further determine thatintent of the voice input is to play the particular song “Hey Jude.”After these determinations, the VAS 190 may transmit a command to aparticular MCS 192 to retrieve content (i.e., the song “Hey Jude”), andthat MCS 192, in turn, provides (e.g., streams) this content directly tothe MPS 100 or indirectly via the VAS 190. In some implementations, theVAS 190 may transmit to the MPS 100 a command that causes the MPS 100itself to retrieve the content from the MCS 192.

In certain implementations, NMDs may facilitate arbitration amongst oneanother when voice input is identified in speech detected by two or moreNMDs located within proximity of one another. For example, theNMD-equipped playback device 102 d in the environment 101 (FIG. 1A) isin relatively close proximity to the NMD-equipped Living Room playbackdevice 102 m, and both devices 102 d and 102 m may at least sometimesdetect the same sound. In such cases, this may require arbitration as towhich device is ultimately responsible for providing detected-sound datato the remote VAS. Examples of arbitrating between NMDs may be found,for example, in previously referenced U.S. application Ser. No.15/438,749.

In certain implementations, an NMD may be assigned to, or otherwiseassociated with, a designated or default playback device that may notinclude an NMD. For example, the Island NMD 103 f in the Kitchen 101 h(FIG. 1A) may be assigned to the Dining Room playback device 102 l,which is in relatively close proximity to the Island NMD 103 f Inpractice, an NMD may direct an assigned playback device to play audio inresponse to a remote VAS receiving a voice input from the NMD to playthe audio, which the NMD might have sent to the VAS in response to auser speaking a command to play a certain song, album, playlist, etc.Additional details regarding assigning NMDs and playback devices asdesignated or default devices may be found, for example, in previouslyreferenced U.S. patent application Ser. No. 15/438,749.

Further aspects relating to the different components of the example MPS100 and how the different components may interact to provide a user witha media experience may be found in the following sections. Whilediscussions herein may generally refer to the example MPS 100,technologies described herein are not limited to applications within,among other things, the home environment described above. For instance,the technologies described herein may be useful in other homeenvironment configurations comprising more or fewer of any of theplayback, network microphone, and/or controller devices 102-104. Forexample, the technologies herein may be utilized within an environmenthaving a single playback device 102 and/or a single NMD 103. In someexamples of such cases, the LAN 101 (FIG. 1B) may be eliminated and thesingle playback device 102 and/or the single NMD 103 may communicatedirectly with the remote computing devices 106 a-d. In some embodiments,a telecommunication network (e.g., an LTE network, a 5G network, etc.)may communicate with the various playback, network microphone, and/orcontroller devices 102-104 independent of a LAN.

a. Example Playback & Network Microphone Devices

FIG. 2A is a functional block diagram illustrating certain aspects ofone of the playback devices 102 of the MPS 100 of FIGS. 1A and 1B. Asshown, the playback device 102 includes various components, each ofwhich is discussed in further detail below, and the various componentsof the playback device 102 may be operably coupled to one another via asystem bus, communication network, or some other connection mechanism.In the illustrated example of FIG. 2A, the playback device 102 may bereferred to as an “NMD-equipped” playback device because it includescomponents that support the functionality of an NMD, such as one of theNMDs 103 shown in FIG. 1A.

As shown, the playback device 102 includes at least one processor 212,which may be a clock-driven computing component configured to processinput data according to instructions stored in memory 213. The memory213 may be a tangible, non-transitory, computer-readable mediumconfigured to store instructions that are executable by the processor212. For example, the memory 213 may be data storage that can be loadedwith software code 214 that is executable by the processor 212 toachieve certain functions.

In one example, these functions may involve the playback device 102retrieving audio data from an audio source, which may be anotherplayback device. In another example, the functions may involve theplayback device 102 sending audio data, detected-sound data (e.g.,corresponding to a voice input), and/or other information to anotherdevice on a network via at least one network interface 224. In yetanother example, the functions may involve the playback device 102causing one or more other playback devices to synchronously playbackaudio with the playback device 102. In yet a further example, thefunctions may involve the playback device 102 facilitating being pairedor otherwise bonded with one or more other playback devices to create amulti-channel audio environment. Numerous other example functions arepossible, some of which are discussed below.

As just mentioned, certain functions may involve the playback device 102synchronizing playback of audio content with one or more other playbackdevices. During synchronous playback, a listener may not perceivetime-delay differences between playback of the audio content by thesynchronized playback devices. U.S. Pat. No. 8,234,395 filed on Apr. 4,2004, and titled “System and method for synchronizing operations among aplurality of independently clocked digital data processing devices,”which is hereby incorporated by reference in its entirety, provides inmore detail some examples for audio playback synchronization amongplayback devices.

To facilitate audio playback, the playback device 102 includes audioprocessing components 216 that are generally configured to process audioprior to the playback device 102 rendering the audio. In this respect,the audio processing components 216 may include one or moredigital-to-analog converters (“DAC”), one or more audio preprocessingcomponents, one or more audio enhancement components, one or moredigital signal processors (“DSPs”), and so on. In some implementations,one or more of the audio processing components 216 may be a subcomponentof the processor 212. In operation, the audio processing components 216receive analog and/or digital audio and process and/or otherwiseintentionally alter the audio to produce audio signals for playback.

The produced audio signals may then be provided to one or more audioamplifiers 217 for amplification and playback through one or morespeakers 218 operably coupled to the amplifiers 217. The audioamplifiers 217 may include components configured to amplify audiosignals to a level for driving one or more of the speakers 218.

Each of the speakers 218 may include an individual transducer (e.g., a“driver”) or the speakers 218 may include a complete speaker systeminvolving an enclosure with one or more drivers. A particular driver ofa speaker 218 may include, for example, a subwoofer (e.g., for lowfrequencies), a mid-range driver (e.g., for middle frequencies), and/ora tweeter (e.g., for high frequencies). In some cases, a transducer maybe driven by an individual corresponding audio amplifier of the audioamplifiers 217. In some implementations, a playback device may notinclude the speakers 218, but instead may include a speaker interfacefor connecting the playback device to external speakers. In certainembodiments, a playback device may include neither the speakers 218 northe audio amplifiers 217, but instead may include an audio interface(not shown) for connecting the playback device to an external audioamplifier or audio-visual receiver.

In addition to producing audio signals for playback by the playbackdevice 102, the audio processing components 216 may be configured toprocess audio to be sent to one or more other playback devices, via thenetwork interface 224, for playback. In example scenarios, audio contentto be processed and/or played back by the playback device 102 may bereceived from an external source, such as via an audio line-in interface(e.g., an auto-detecting 3.5 mm audio line-in connection) of theplayback device 102 (not shown) or via the network interface 224, asdescribed below.

As shown, the at least one network interface 224, may take the form ofone or more wireless interfaces 225 and/or one or more wired interfaces226. A wireless interface may provide network interface functions forthe playback device 102 to wirelessly communicate with other devices(e.g., other playback device(s), NMD(s), and/or controller device(s)) inaccordance with a communication protocol (e.g., any wireless standardincluding IEEE 1002.11a, 1002.11b, 1002.11g, 1002.11n, 1002.11ac,1002.15, 4G mobile communication standard, and so on). A wired interfacemay provide network interface functions for the playback device 102 tocommunicate over a wired connection with other devices in accordancewith a communication protocol (e.g., IEEE 1002.3). While the networkinterface 224 shown in FIG. 2A include both wired and wirelessinterfaces, the playback device 102 may in some implementations includeonly wireless interface(s) or only wired interface(s).

In general, the network interface 224 facilitates data flow between theplayback device 102 and one or more other devices on a data network. Forinstance, the playback device 102 may be configured to receive audiocontent over the data network from one or more other playback devices,network devices within a LAN, and/or audio content sources over a WAN,such as the Internet. In one example, the audio content and othersignals transmitted and received by the playback device 102 may betransmitted in the form of digital packet data comprising an InternetProtocol (IP)-based source address and IP-based destination addresses.In such a case, the network interface 224 may be configured to parse thedigital packet data such that the data destined for the playback device102 is properly received and processed by the playback device 102.

As shown in FIG. 2A, the playback device 102 also includes voiceprocessing components 220 that are operably coupled to one or moremicrophones 222. The microphones 222 are configured to detect sound(i.e., acoustic waves) in the environment of the playback device 102,which is then provided to the voice processing components 220. Morespecifically, each microphone 222 is configured to detect sound andconvert the sound into a digital or analog signal representative of thedetected sound, which can then cause the voice processing component 220to perform various functions based on the detected sound, as describedin greater detail below. In one implementation, the microphones 222 arearranged as an array of microphones (e.g., an array of six microphones).In some implementations, the playback device 102 includes more than sixmicrophones (e.g., eight microphones or twelve microphones) or fewerthan six microphones (e.g., four microphones, two microphones, or asingle microphones).

In operation, the voice-processing components 220 are generallyconfigured to detect and process sound received via the microphones 222,identify potential voice input in the detected sound, and extractdetected-sound data to enable a VAS, such as the VAS 190 (FIG. 1B), toprocess voice input identified in the detected-sound data. The voiceprocessing components 220 may include one or more analog-to-digitalconverters, an acoustic echo canceller (“AEC”), a spatial processor(e.g., one or more multi-channel Wiener filters, one or more otherfilters, and/or one or more beam former components), one or more buffers(e.g., one or more circular buffers), one or more wake-word engines, oneor more voice extractors, and/or one or more speech processingcomponents (e.g., components configured to recognize a voice of aparticular user or a particular set of users associated with ahousehold), among other example voice processing components. In exampleimplementations, the voice processing components 220 may include orotherwise take the form of one or more DSPs or one or more modules of aDSP. In this respect, certain voice processing components 220 may beconfigured with particular parameters (e.g., gain and/or spectralparameters) that may be modified or otherwise tuned to achieveparticular functions. In some implementations, one or more of the voiceprocessing components 220 may be a subcomponent of the processor 212.

In some implementations, the voice-processing components 220 may detectand store a user's voice profile, which may be associated with a useraccount of the MPS 100. For example, voice profiles may be stored asand/or compared to variables stored in a set of command information ordata table. The voice profile may include aspects of the tone orfrequency of a user's voice and/or other unique aspects of the user'svoice, such as those described in previously-referenced U.S. patentapplication Ser. No. 15/438,749.

As further shown in FIG. 2A, the playback device 102 also includes powercomponents 227. The power components 227 include at least an externalpower source interface 228, which may be coupled to a power source (notshown) via a power cable or the like that physically connects theplayback device 102 to an electrical outlet or some other external powersource. Other power components may include, for example, transformers,converters, and like components configured to format electrical power.

In some implementations, the power components 227 of the playback device102 may additionally include an internal power source 229 (e.g., one ormore batteries) configured to power the playback device 102 without aphysical connection to an external power source. When equipped with theinternal power source 229, the playback device 102 may operateindependent of an external power source. In some such implementations,the external power source interface 228 may be configured to facilitatecharging the internal power source 229. As discussed before, a playbackdevice comprising an internal power source may be referred to herein asa “portable playback device.” On the other hand, a playback device thatoperates using an external power source may be referred to herein as a“stationary playback device,” although such a device may in fact bemoved around a home or other environment.

The playback device 102 further includes a user interface 240 that mayfacilitate user interactions independent of or in conjunction with userinteractions facilitated by one or more of the controller devices 104.In various embodiments, the user interface 240 includes one or morephysical buttons and/or supports graphical interfaces provided on touchsensitive screen(s) and/or surface(s), among other possibilities, for auser to directly provide input. The user interface 240 may furtherinclude one or more of lights (e.g., LEDs) and the speakers to providevisual and/or audio feedback to a user.

As an illustrative example, FIG. 2B shows an example housing 230 of theplayback device 102 that includes a user interface in the form of acontrol area 232 at a top portion 234 of the housing 230. The controlarea 232 includes buttons 236 a-c for controlling audio playback, volumelevel, and other functions. The control area 232 also includes a button236 d for toggling the microphones 222 to either an on state or an offstate.

As further shown in FIG. 2B, the control area 232 is at least partiallysurrounded by apertures formed in the top portion 234 of the housing 230through which the microphones 222 (not visible in FIG. 2B) receive thesound in the environment of the playback device 102. The microphones 222may be arranged in various positions along and/or within the top portion234 or other areas of the housing 230 so as to detect sound from one ormore directions relative to the playback device 102.

By way of illustration, SONOS, Inc. presently offers (or has offered)for sale certain playback devices that may implement certain of theembodiments disclosed herein, including a “PLAY:1,” “PLAY:3,” “PLAY:5,”“PLAYBAR,” “CONNECT:AMP,” “PLAYBASE,” “BEAM,” “CONNECT,” and “SUB.” Anyother past, present, and/or future playback devices may additionally oralternatively be used to implement the playback devices of exampleembodiments disclosed herein. Additionally, it should be understood thata playback device is not limited to the examples illustrated in FIG. 2Aor 2B or to the SONOS product offerings. For example, a playback devicemay include, or otherwise take the form of, a wired or wirelessheadphone set, which may operate as a part of the media playback system100 via a network interface or the like. In another example, a playbackdevice may include or interact with a docking station for personalmobile media playback devices. In yet another example, a playback devicemay be integral to another device or component such as a television, alighting fixture, or some other device for indoor or outdoor use.

b. Example Playback Device Configurations

FIGS. 3A-3E show example configurations of playback devices. Referringfirst to FIG. 3A, in some example instances, a single playback devicemay belong to a zone. For example, the playback device 102 c (FIG. 1A)on the Patio may belong to Zone A. In some implementations describedbelow, multiple playback devices may be “bonded” to form a “bonded pair”which together form a single zone. For example, the playback device 102f (FIG. 1A) named “Bed 1” in FIG. 3A may be bonded to the playbackdevice 102 g (FIG. 1A) named “Bed 2” in FIG. 3A to form Zone B. Bondedplayback devices may have different playback responsibilities (e.g.,channel responsibilities). In another implementation described below,multiple playback devices may be merged to form a single zone. Forexample, the playback device 102 d named “Bookcase” may be merged withthe playback device 102 m named “Living Room” to form a single Zone C.The merged playback devices 102 d and 102 m may not be specificallyassigned different playback responsibilities. That is, the mergedplayback devices 102 d and 102 m may, aside from playing audio contentin synchrony, each play audio content as they would if they were notmerged.

For purposes of control, each zone in the MPS 100 may be represented asa single user interface (“UI”) entity. For example, as displayed by thecontroller devices 104, Zone A may be provided as a single entity named“Portable,” Zone B may be provided as a single entity named “Stereo,”and Zone C may be provided as a single entity named “Living Room.”

In various embodiments, a zone may take on the name of one of theplayback devices belonging to the zone. For example, Zone C may take onthe name of the Living Room device 102 m (as shown). In another example,Zone C may instead take on the name of the Bookcase device 102 d. In afurther example, Zone C may take on a name that is some combination ofthe Bookcase device 102 d and Living Room device 102 m. The name that ischosen may be selected by a user via inputs at a controller device 104.In some embodiments, a zone may be given a name that is different thanthe device(s) belonging to the zone. For example, Zone B in FIG. 3A isnamed “Stereo” but none of the devices in Zone B have this name. In oneaspect, Zone B is a single UI entity representing a single device named“Stereo,” composed of constituent devices “Bed 1” and “Bed 2.” In oneimplementation, the Bed 1 device may be playback device 102 f in themaster bedroom 101 h (FIG. 1A) and the Bed 2 device may be the playbackdevice 102 g also in the master bedroom 101 h (FIG. 1A).

As noted above, playback devices that are bonded may have differentplayback responsibilities, such as playback responsibilities for certainaudio channels. For example, as shown in FIG. 3B, the Bed 1 and Bed 2devices 102 f and 102 g may be bonded so as to produce or enhance astereo effect of audio content. In this example, the Bed 1 playbackdevice 102 f may be configured to play a left channel audio component,while the Bed 2 playback device 102 g may be configured to play a rightchannel audio component. In some implementations, such stereo bondingmay be referred to as “pairing.”

Additionally, playback devices that are configured to be bonded may haveadditional and/or different respective speaker drivers. As shown in FIG.3C, the playback device 102 b named “Front” may be bonded with theplayback device 102 k named “SUB.” The Front device 102 b may render arange of mid to high frequencies, and the SUB device 102 k may renderlow frequencies as, for example, a subwoofer. When unbonded, the Frontdevice 102 b may be configured to render a full range of frequencies. Asanother example, FIG. 3D shows the Front and SUB devices 102 b and 102 kfurther bonded with Right and Left playback devices 102 a and 102 j,respectively. In some implementations, the Right and Left devices 102 aand 102 j may form surround or “satellite” channels of a home theatersystem. The bonded playback devices 102 a, 102 b, 102 j, and 102 k mayform a single Zone D (FIG. 3A).

In some implementations, playback devices may also be “merged.” Incontrast to certain bonded playback devices, playback devices that aremerged may not have assigned playback responsibilities, but may eachrender the full range of audio content that each respective playbackdevice is capable of. Nevertheless, merged devices may be represented asa single UI entity (i.e., a zone, as discussed above). For instance,FIG. 3E shows the playback devices 102 d and 102 m in the Living Roommerged, which would result in these devices being represented by thesingle UI entity of Zone C. In one embodiment, the playback devices 102d and 102 m may playback audio in synchrony, during which each outputsthe full range of audio content that each respective playback device 102d and 102 m is capable of rendering.

In some embodiments, a stand-alone NMD may be in a zone by itself. Forexample, the NMD 103 h from FIG. 1A is named “Closet” and forms Zone Iin FIG. 3A. An NMD may also be bonded or merged with another device soas to form a zone. For example, the NMD device 103 f named “Island” maybe bonded with the playback device 102 i Kitchen, which together formZone F, which is also named “Kitchen.” Additional details regardingassigning NMDs and playback devices as designated or default devices maybe found, for example, in previously referenced U.S. patent applicationSer. No. 15/438,749. In some embodiments, a stand-alone NMD may not beassigned to a zone.

Zones of individual, bonded, and/or merged devices may be arranged toform a set of playback devices that playback audio in synchrony. Such aset of playback devices may be referred to as a “group,” “zone group,”“synchrony group,” or “playback group.” In response to inputs providedvia a controller device 104, playback devices may be dynamically groupedand ungrouped to form new or different groups that synchronously playback audio content. For example, referring to FIG. 3A, Zone A may begrouped with Zone B to form a zone group that includes the playbackdevices of the two zones. As another example, Zone A may be grouped withone or more other Zones C-I. The Zones A-I may be grouped and ungroupedin numerous ways. For example, three, four, five, or more (e.g., all) ofthe Zones A-I may be grouped. When grouped, the zones of individualand/or bonded playback devices may play back audio in synchrony with oneanother, as described in previously referenced U.S. Pat. No. 8,234,395.Grouped and bonded devices are example types of associations betweenportable and stationary playback devices that may be caused in responseto a trigger event, as discussed above and described in greater detailbelow.

In various implementations, the zones in an environment may be assigneda particular name, which may be the default name of a zone within a zonegroup or a combination of the names of the zones within a zone group,such as “Dining Room+Kitchen,” as shown in FIG. 3A. In some embodiments,a zone group may be given a unique name selected by a user, such as“Nick's Room,” as also shown in FIG. 3A. The name “Nick's Room” may be aname chosen by a user over a prior name for the zone group, such as theroom name “Master Bedroom.”

Referring back to FIG. 2A, certain data may be stored in the memory 213as one or more state variables that are periodically updated and used todescribe the state of a playback zone, the playback device(s), and/or azone group associated therewith. The memory 213 may also include thedata associated with the state of the other devices of the mediaplayback system 100, which may be shared from time to time among thedevices so that one or more of the devices have the most recent dataassociated with the system.

In some embodiments, the memory 213 of the playback device 202 may storeinstances of various variable types associated with the states.Variables instances may be stored with identifiers (e.g., tags)corresponding to type. For example, certain identifiers may be a firsttype “a1” to identify playback device(s) of a zone, a second type “b1”to identify playback device(s) that may be bonded in the zone, and athird type “c1” to identify a zone group to which the zone may belong.As a related example, in FIG. 1A, identifiers associated with the Patiomay indicate that the Patio is the only playback device of a particularzone and not in a zone group. Identifiers associated with the LivingRoom may indicate that the Living Room is not grouped with other zonesbut includes bonded playback devices 102 a, 102 b, 102 j, and 102 k.Identifiers associated with the Dining Room may indicate that the DiningRoom is part of Dining Room+Kitchen group and that devices 103 f and 102i are bonded. Identifiers associated with the Kitchen may indicate thesame or similar information by virtue of the Kitchen being part of theDining Room+Kitchen zone group. Other example zone variables andidentifiers are described below.

In yet another example, the MPS 100 may include variables or identifiersrepresenting other associations of zones and zone groups, such asidentifiers associated with Areas, as shown in FIG. 3A. An Area mayinvolve a cluster of zone groups and/or zones not within a zone group.For instance, FIG. 3A shows a first area named “First Area” and a secondarea named “Second Area.” The First Area includes zones and zone groupsof the Patio, Den, Dining Room, Kitchen, and Bathroom. The Second Areaincludes zones and zone groups of the Bathroom, Nick's Room, Bedroom,and Living Room. In one aspect, an Area may be used to invoke a clusterof zone groups and/or zones that share one or more zones and/or zonegroups of another cluster. In this respect, such an Area differs from azone group, which does not share a zone with another zone group. Furtherexamples of techniques for implementing Areas may be found, for example,in U.S. application Ser. No. 15/682,506 filed Aug. 21, 2017 and titled“Room Association Based on Name,” and U.S. Pat. No. 8,483,853 filed Sep.11, 2007, and titled “Controlling and manipulating groupings in amulti-zone media system.” Each of these applications is incorporatedherein by reference in its entirety. In some embodiments, the MPS 100may not implement Areas, in which case the system may not storevariables associated with Areas.

The memory 213 may be further configured to store other data. Such datamay pertain to audio sources accessible by the playback device 102 or aplayback queue that the playback device (or some other playbackdevice(s)) may be associated with. In embodiments described below, thememory 213 is configured to store a set of command data for selecting aparticular VAS when processing voice inputs.

During operation, one or more playback zones in the environment of FIG.1A may each be playing different audio content. For instance, the usermay be grilling in the Patio zone and listening to hip hop music beingplayed by the playback device 102 c, while another user may be preparingfood in the Kitchen zone and listening to classical music being playedby the playback device 102 i. In another example, a playback zone mayplay the same audio content in synchrony with another playback zone. Forinstance, the user may be in the Office zone where the playback device102 n is playing the same hip-hop music that is being playing byplayback device 102 c in the Patio zone. In such a case, playbackdevices 102 c and 102 n may be playing the hip-hop in synchrony suchthat the user may seamlessly (or at least substantially seamlessly)enjoy the audio content that is being played out-loud while movingbetween different playback zones. Synchronization among playback zonesmay be achieved in a manner similar to that of synchronization amongplayback devices, as described in previously referenced U.S. Pat. No.8,234,395.

As suggested above, the zone configurations of the MPS 100 may bedynamically modified. As such, the MPS 100 may support numerousconfigurations. For example, if a user physically moves one or moreplayback devices to or from a zone, the MPS 100 may be reconfigured toaccommodate the change(s). For instance, if the user physically movesthe playback device 102 c from the Patio zone to the Office zone, theOffice zone may now include both the playback devices 102 c and 102 n.In some cases, the user may pair or group the moved playback device 102c with the Office zone and/or rename the players in the Office zoneusing, for example, one of the controller devices 104 and/or voiceinput. As another example, if one or more playback devices 102 are movedto a particular space in the home environment that is not already aplayback zone, the moved playback device(s) may be renamed or associatedwith a playback zone for the particular space.

Further, different playback zones of the MPS 100 may be dynamicallycombined into zone groups or split up into individual playback zones.For example, the Dining Room zone and the Kitchen zone may be combinedinto a zone group for a dinner party such that playback devices 102 iand 102 l may render audio content in synchrony. As another example,bonded playback devices in the Den zone may be split into (i) atelevision zone and (ii) a separate listening zone. The television zonemay include the Front playback device 102 b. The listening zone mayinclude the Right, Left, and SUB playback devices 102 a, 102 j, and 102k, which may be grouped, paired, or merged, as described above.Splitting the Den zone in such a manner may allow one user to listen tomusic in the listening zone in one area of the living room space, andanother user to watch the television in another area of the living roomspace. In a related example, a user may utilize either of the NMD 103 aor 103 b (FIG. 1B) to control the Den zone before it is separated intothe television zone and the listening zone. Once separated, thelistening zone may be controlled, for example, by a user in the vicinityof the NMD 103 a, and the television zone may be controlled, forexample, by a user in the vicinity of the NMD 103 b. As described above,however, any of the NMDs 103 may be configured to control the variousplayback and other devices of the MPS 100.

c. Example Controller Devices

FIG. 4A is a functional block diagram illustrating certain aspects of aselected one of the controller devices 104 of the MPS 100 of FIG. 1A.Such controller devices may also be referred to herein as a “controldevice” or “controller.” The controller device shown in FIG. 4A mayinclude components that are generally similar to certain components ofthe network devices described above, such as a processor 412, memory 413storing program software 414, at least one network interface 424, andone or more microphones 422. In one example, a controller device may bea dedicated controller for the MPS 100. In another example, a controllerdevice may be a network device on which media playback system controllerapplication software may be installed, such as for example, an iPhone™,iPad™ or any other smart phone, tablet, or network device (e.g., anetworked computer such as a PC or Mac™).

The memory 413 of the controller device 104 may be configured to storecontroller application software and other data associated with the MPS100 and/or a user of the system 100. The memory 413 may be loaded withinstructions in software 414 that are executable by the processor 412 toachieve certain functions, such as facilitating user access, control,and/or configuration of the MPS 100. The controller device 104 isconfigured to communicate with other network devices via the networkinterface 424, which may take the form of a wireless interface, asdescribed above.

In one example, system information (e.g., such as a state variable) maybe communicated between the controller device 104 and other devices viathe network interface 424. For instance, the controller device 104 mayreceive playback zone and zone group configurations in the MPS 100 froma playback device, an NMD, or another network device. Likewise, thecontroller device 104 may transmit such system information to a playbackdevice or another network device via the network interface 424. In somecases, the other network device may be another controller device.

The controller device 104 may also communicate playback device controlcommands, such as volume control and audio playback control, to aplayback device via the network interface 424. As suggested above,changes to configurations of the MPS 100 may also be performed by a userusing the controller device 104. The configuration changes may includeadding/removing one or more playback devices to/from a zone,adding/removing one or more zones to/from a zone group, forming a bondedor merged player, separating one or more playback devices from a bondedor merged player, among others.

As shown in FIG. 4A, the controller device 104 also includes a userinterface 440 that is generally configured to facilitate user access andcontrol of the MPS 100. The user interface 440 may include atouch-screen display or other physical interface configured to providevarious graphical controller interfaces, such as the controllerinterfaces 440 a and 440 b shown in FIGS. 4B and 4C. Referring to FIGS.4B and 4C together, the controller interfaces 440 a and 440 b includes aplayback control region 442, a playback zone region 443, a playbackstatus region 444, a playback queue region 446, and a sources region448. The user interface as shown is just one example of an interfacethat may be provided on a network device, such as the controller deviceshown in FIG. 4A, and accessed by users to control a media playbacksystem, such as the MPS 100. Other user interfaces of varying formats,styles, and interactive sequences may alternatively be implemented onone or more network devices to provide comparable control access to amedia playback system.

The playback control region 442 (FIG. 4B) may include selectable icons(e.g., by way of touch or by using a cursor) that, when selected, causeplayback devices in a selected playback zone or zone group to play orpause, fast forward, rewind, skip to next, skip to previous, enter/exitshuffle mode, enter/exit repeat mode, enter/exit cross fade mode, etc.The playback control region 442 may also include selectable icons that,when selected, modify equalization settings and/or playback volume,among other possibilities.

The playback zone region 443 (FIG. 4C) may include representations ofplayback zones within the MPS 100. The playback zones regions 443 mayalso include a representation of zone groups, such as the DiningRoom+Kitchen zone group, as shown. In some embodiments, the graphicalrepresentations of playback zones may be selectable to bring upadditional selectable icons to manage or configure the playback zones inthe MPS 100, such as a creation of bonded zones, creation of zonegroups, separation of zone groups, and renaming of zone groups, amongother possibilities.

For example, as shown, a “group” icon may be provided within each of thegraphical representations of playback zones. The “group” icon providedwithin a graphical representation of a particular zone may be selectableto bring up options to select one or more other zones in the MPS 100 tobe grouped with the particular zone. Once grouped, playback devices inthe zones that have been grouped with the particular zone will beconfigured to play audio content in synchrony with the playbackdevice(s) in the particular zone. Analogously, a “group” icon may beprovided within a graphical representation of a zone group. In thiscase, the “group” icon may be selectable to bring up options to deselectone or more zones in the zone group to be removed from the zone group.Other interactions and implementations for grouping and ungrouping zonesvia a user interface are also possible. The representations of playbackzones in the playback zone region 443 (FIG. 4C) may be dynamicallyupdated as playback zone or zone group configurations are modified.

The playback status region 444 (FIG. 4B) may include graphicalrepresentations of audio content that is presently being played,previously played, or scheduled to play next in the selected playbackzone or zone group. The selected playback zone or zone group may bevisually distinguished on a controller interface, such as within theplayback zone region 443 and/or the playback status region 444. Thegraphical representations may include track title, artist name, albumname, album year, track length, and/or other relevant information thatmay be useful for the user to know when controlling the MPS 100 via thecontroller interface.

The playback queue region 446 may include graphical representations ofaudio content in a playback queue associated with the selected playbackzone or zone group. In some embodiments, each playback zone or zonegroup may be associated with a playback queue comprising informationcorresponding to zero or more audio items for playback by the playbackzone or zone group. For instance, each audio item in the playback queuemay comprise a uniform resource identifier (URI), a uniform resourcelocator (URL), or some other identifier that may be used by a playbackdevice in the playback zone or zone group to find and/or retrieve theaudio item from a local audio content source or a networked audiocontent source, which may then be played back by the playback device.

In one example, a playlist may be added to a playback queue, in whichcase information corresponding to each audio item in the playlist may beadded to the playback queue. In another example, audio items in aplayback queue may be saved as a playlist. In a further example, aplayback queue may be empty, or populated but “not in use” when theplayback zone or zone group is playing continuously streamed audiocontent, such as Internet radio that may continue to play untilotherwise stopped, rather than discrete audio items that have playbackdurations. In an alternative embodiment, a playback queue can includeInternet radio and/or other streaming audio content items and be “inuse” when the playback zone or zone group is playing those items. Otherexamples are also possible.

When playback zones or zone groups are “grouped” or “ungrouped,”playback queues associated with the affected playback zones or zonegroups may be cleared or re-associated. For example, if a first playbackzone including a first playback queue is grouped with a second playbackzone including a second playback queue, the established zone group mayhave an associated playback queue that is initially empty, that containsaudio items from the first playback queue (such as if the secondplayback zone was added to the first playback zone), that contains audioitems from the second playback queue (such as if the first playback zonewas added to the second playback zone), or a combination of audio itemsfrom both the first and second playback queues. Subsequently, if theestablished zone group is ungrouped, the resulting first playback zonemay be re-associated with the previous first playback queue or may beassociated with a new playback queue that is empty or contains audioitems from the playback queue associated with the established zone groupbefore the established zone group was ungrouped. Similarly, theresulting second playback zone may be re-associated with the previoussecond playback queue or may be associated with a new playback queuethat is empty or contains audio items from the playback queue associatedwith the established zone group before the established zone group wasungrouped. Other examples are also possible.

With reference still to FIGS. 4B and 4C, the graphical representationsof audio content in the playback queue region 446 (FIG. 4B) may includetrack titles, artist names, track lengths, and/or other relevantinformation associated with the audio content in the playback queue. Inone example, graphical representations of audio content may beselectable to bring up additional selectable icons to manage and/ormanipulate the playback queue and/or audio content represented in theplayback queue. For instance, a represented audio content may be removedfrom the playback queue, moved to a different position within theplayback queue, or selected to be played immediately, or after anycurrently playing audio content, among other possibilities. A playbackqueue associated with a playback zone or zone group may be stored in amemory on one or more playback devices in the playback zone or zonegroup, on a playback device that is not in the playback zone or zonegroup, and/or some other designated device. Playback of such a playbackqueue may involve one or more playback devices playing back media itemsof the queue, perhaps in sequential or random order.

The sources region 448 may include graphical representations ofselectable audio content sources and/or selectable voice assistantsassociated with a corresponding VAS. The VASes may be selectivelyassigned. In some examples, multiple VASes, such as AMAZON's Alexa,MICROSOFT's Cortana, etc., may be invokable by the same NMD. In someembodiments, a user may assign a VAS exclusively to one or more NMDs.For example, a user may assign a first VAS to one or both of the NMDs102 a and 102 b in the Living Room shown in FIG. 1A, and a second VAS tothe NMD 103 f in the Kitchen. Other examples are possible.

d. Example Audio Content Sources

The audio sources in the sources region 448 may be audio content sourcesfrom which audio content may be retrieved and played by the selectedplayback zone or zone group. One or more playback devices in a zone orzone group may be configured to retrieve for playback audio content(e.g., according to a corresponding URI or URL for the audio content)from a variety of available audio content sources. In one example, audiocontent may be retrieved by a playback device directly from acorresponding audio content source (e.g., via a line-in connection). Inanother example, audio content may be provided to a playback device overa network via one or more other playback devices or network devices. Asdescribed in greater detail below, in some embodiments audio content maybe provided by one or more media content services.

Example audio content sources may include a memory of one or moreplayback devices in a media playback system such as the MPS 100 of FIG.1, local music libraries on one or more network devices (e.g., acontroller device, a network-enabled personal computer, or anetworked-attached storage (“NAS”)), streaming audio services providingaudio content via the Internet (e.g., cloud-based music services), oraudio sources connected to the media playback system via a line-in inputconnection on a playback device or network device, among otherpossibilities.

In some embodiments, audio content sources may be added or removed froma media playback system such as the MPS 100 of FIG. 1A. In one example,an indexing of audio items may be performed whenever one or more audiocontent sources are added, removed, or updated. Indexing of audio itemsmay involve scanning for identifiable audio items in allfolders/directories shared over a network accessible by playback devicesin the media playback system and generating or updating an audio contentdatabase comprising metadata (e.g., title, artist, album, track length,among others) and other associated information, such as a URI or URL foreach identifiable audio item found. Other examples for managing andmaintaining audio content sources may also be possible.

e. Example Network Microphone Devices

FIG. 5 is a functional block diagram showing an NMD 503 configured inaccordance with embodiments of the disclosure. The NMD 503 includesvoice capture components (“VCC”) 560; at least one wake-word engine 570and at least one voice extractor 572, each of which is operably coupledto the VCC 560; and a local arbitrator 576, audio output processingcomponents 515 operably coupled to the local arbitrator 576, and atleast one audio input interface 519 operably coupled to the audio outputprocessing components 515, both of which may form a portion of the audioprocessing components 216 discussed above. The NMD 503 further includesthe microphones 222 and the at least one network interface 224 describedabove and may also include other components, such as audio amplifiers,speakers, a user interface, etc., which are not shown in FIG. 5 forpurposes of clarity.

The microphones 222 of the NMD 503 are configured to provide detectedsound, S_(D), from the environment of the NMD 503 to the VCC 560. Thedetected sound S_(D) may take the form of one or more analog or digitalsignals. In example implementations, the detected sound S_(D) may becomposed of a plurality signals associated with respective channels 562that are fed to the VCC 560.

Each channel 562 may correspond to a particular microphone 222. Forexample, an NMD having six microphones may have six correspondingchannels. Each channel of the detected sound S_(D) may bear certainsimilarities to the other channels but may differ in certain regards,which may be due to the position of the given channel's correspondingmicrophone relative to the microphones of other channels. For example,one or more of the channels of the detected sound S_(D) may have agreater signal to noise ratio (“SNR”) of speech to background noise thanother channels.

As further shown in FIG. 5, the VCC 560 includes an AEC 564, a spatialprocessor 566, and one or more buffers 568. In operation, the AEC 564receives the detected sound S_(D) and filters or otherwise processes thesound to suppress echoes and/or to otherwise improve the quality of thedetected sound S_(D). That processed sound may then be passed to thespatial processor 566.

The spatial processor 566 is typically configured to analyze thedetected sound S_(D) and identify certain characteristics, such as asound's amplitude (e.g., decibel level), frequency spectrum,directionality, etc. In one respect, the spatial processor 566 may helpfilter or suppress ambient noise in the detected sound S_(D) frompotential user speech based on similarities and differences in theconstituent channels 562 of the detected sound S_(D), as discussedabove. As one possibility, the spatial processor 566 may monitor metricsthat distinguish speech from other sounds. Such metrics can include, forexample, energy within the speech band relative to background noise andentropy within the speech band—a measure of spectral structure—which istypically lower in speech than in most common background noise. In someimplementations, the spatial processor 566 may be configured todetermine a speech presence probability, examples of such functionalityare disclosed in U.S. patent application Ser. No. 15/984,073, filed May18, 2018, titled “Linear Filtering for Noise-Suppressed SpeechDetection,” which is incorporated herein by reference in its entirety.

In operation, the one or more buffers 568—one or more of which may bepart of or separate from the memory 213 (FIG. 2A)—capture datacorresponding to the detected sound S_(D). More specifically, the one ormore buffers 568 capture detected-sound data that was processed by theupstream AEC 564 and spatial processor 566. In some implementations, theNMD 503 may include an additional buffer 569 (shown in dashed lines)that stores information (e.g., metadata or the like) regarding thedetected sound S_(D) that was processed by the upstream AEC 564 andspatial processor 566. This other buffer 569 may be referred to as a“sound metadata buffer.” When the wake-word engine 570 identifies awake-word trigger (discussed below), the sound metadata buffer 569 maypass to the network interface 224 sound characteristic informationcorresponding to the wake-word trigger (e.g., spectral and/or gaininformation of the environment of the NMD and/or the voice inputcomprising the wake word). The network interface 224 may then providethis information to a remote server that may be associated, e.g., withthe MPS 100. In one aspect, the information stored in the additionalbuffer 569 does not reveal the content of any speech but instead isindicative of certain unique features of the detected sound itself. In arelated aspect, the metadata may be communicated between computingdevices, such as the various computing devices of the MPS 100 withoutimplicating privacy concerns. In practice, the MPS 100 can use the datato adapt and fine-tune voice processing algorithms, includingsensitivity tuning as discussed below.

In any event, the detected-sound data form a digital representation(i.e., sound-data stream), S_(DS), of the sound detected by themicrophones 222. In practice, the sound-data stream S_(DS) may take avariety of forms. As one possibility, the sound-data stream S_(DS) maybe composed of frames, each of which may include one or more soundsamples. The frames may be streamed (i.e., read out) from the one ormore buffers 568 for further processing by downstream components, suchas the wake-word engine 570 and the voice extractor 572 of the NMD 503.

In some implementations, at least one buffer 568 captures detected-sounddata utilizing a sliding window approach in which a given amount (i.e.,a given window) of the most recently captured detected-sound data isretained in the at least one buffer 568 while older detected-sound dataare overwritten when they fall outside of the window. For example, atleast one buffer 568 may temporarily retain 20 frames of a soundspecimen at given time, discard the oldest frame after an expirationtime, and then capture a new frame, which is added to the 19 priorframes of the sound specimen.

In practice, when the sound-data stream S_(DS) is composed of frames,the frames may take a variety of forms having a variety ofcharacteristics. As one possibility, the frames may take the form ofaudio frames that have a certain resolution (e.g., 16 bits ofresolution), which may be based on a sampling rate (e.g., 44,100 Hz).Additionally, or alternatively, the frames may include informationcorresponding to a given sound specimen that the frames define, such asmetadata that indicates frequency response, power input level, SNR,microphone channel identification, and/or other information of the givensound specimen, among other examples. Thus, in some embodiments, a framemay include a portion of sound (e.g., one or more samples of a givensound specimen) and metadata regarding the portion of sound. In otherembodiments, a frame may only include a portion of sound (e.g., one ormore samples of a given sound specimen) or metadata regarding a portionof sound.

In any case, downstream components of the NMD 503 may process thesound-data stream S_(DS). For instance, the wake-word engine 570 isconfigured to apply or more identification algorithms to the sound-datastream S_(DS) (e.g., streamed sound frames) to spot potential wake wordsin the detected-sound S_(D). When the wake-word engine 570 spots apotential wake word, the work-word engine 570 provides an indication ofa “wake-word event” (also referred to as a “wake-word trigger”). In theillustrated example of FIG. 5, the wake-word engine 570 outputs asignal, S_(W), that indicates the occurrence of a wake-word event to thevoice extractor 572.

In multi-VAS implementations, the NMD 503 may include a VAS selector 574(shown in dashed lines) that is generally configured to direct the voiceextractor's extraction and transmission of the sound-data stream S_(DS)to the appropriate VAS when a given wake-word is identified by aparticular wake-word engine (and a corresponding wake-word trigger),such as the wake-word engine 570 and at least one additional wake-wordengine 571 (shown in dashed lines). In such implementations, the NMD 503may include multiple, different wake-word engines and/or voiceextractors, each supported by a particular VAS. Similar to thediscussion above, each wake-word engine may be configured to receive asinput the sound-data stream S_(DS) from the one or more buffers 568 andapply identification algorithms to cause a wake-word trigger for theappropriate VAS. Thus, as one example, the wake-word engine 570 may beconfigured to identify the wake word “Alexa” and cause the NMD 503 toinvoke the AMAZON VAS when “Alexa” is spotted. As another example, thewake-word engine 571 may be configured to identify the wake word “Ok,Google” and cause the NMD 503 to invoke the GOOGLE VAS when “Ok, Google”is spotted. In single-VAS implementations, the VAS selector 574 may beomitted.

In response to the wake-word event (e.g., in response to the signalS_(W) indicating the wake-word event), the voice extractor 572 isconfigured to receive and format (e.g., packetize) the sound-data streamS_(DS). For instance, the voice extractor 572 packetizes the frames ofthe sound-data stream S_(DS) into messages.

After the voice extractor 572 packetizes the frames of the sound-datastream S_(DS) into messages, the NMD 503 may perform some form ofextraction. The extraction may take various forms which will now bedescribed.

According to one implementation, referred to as “extraction” (and asopposed to “local extraction”), the voice extractor 572 transmits orstreams these messages, M_(V), that may contain voice input in real timeor near real time to a remote VAS, such as the VAS 190 (FIG. 1B), viathe network interface 224. The VAS 190 may receive the messages of thesound-data stream from NMD 503 and any other NMDs that have identified asame wake word based on a detected sound.

According to the local extraction implementation, the voice extractor572 transmits or streams these messages, M_(V), that may contain voiceinput in real time or near real time to local (e.g., playback or networkmicrophone) device on the same local area network as NMD 503 via thenetwork interface 224. The local device receives messages of thesound-data stream from NMD 503 and any other NMDs that have identified asame wake word based and performs arbitration by selecting the NMD thatidentified the given wake word with the highest confidence level.

In any case, The VAS is configured to process the sound-data streamS_(DS) contained in the messages M_(V) sent from the NMD 503. Morespecifically, the VAS is configured to identify voice input based on thesound-data stream S_(DS). Referring to FIG. 6, a voice input 680 mayinclude a wake word portion 680 a and a voice utterance portion 680 b.The wake word portion 680 a corresponds to detected sound that causedthe wake-word event. For instance, the wake word portion 680 acorresponds to detected sound that caused the wake-word engine 570 tooutput the wake word event signal S_(W) to the voice extractor 572. Thevoice utterance portion 680 b corresponds to detected sound thatpotentially comprises a user request following the wake-word portion 680a.

In the standard extraction implementation, the VAS may first process thewake word portion 680 a within the sound-data stream S_(DS) to verifythe presence of the wake word. In some instances, the VAS may determinethat the wake word portion 680 a comprises a false wake word (e.g., theword “Election” when the word “Alexa” is the target wake word). In suchan occurrence, the VAS may send a response to the NMD 503 (FIG. 5) withan indication for the NMD 503 to cease extraction of sound data, whichmay cause the voice extractor 572 to cease further streaming of thedetected-sound data to the VAS. The wake-word engine 570 may resume orcontinue monitoring sound specimens until it spots another potentialwake word, leading to another wake-word event. In some implementations,the VAS may not process or receive the wake word portion 680 a butinstead processes only the voice utterance portion 680 b.

In any case, the VAS processes the voice utterance portion 680 b toidentify the presence of any words in the detected-sound data and todetermine an underlying intent from these words. The words maycorrespond to a certain command and certain keywords 684 (identifiedindividually in FIG. 6 as a first keyword 684 a and a second keyword 684b). A keyword may be, for example, a word in the voice input 680identifying a particular device or group in the MPS 100. For instance,in the illustrated example, the keywords 684 may be one or more wordsidentifying one or more zones in which the music is to be played, suchas the Living Room and the Dining Room (FIG. 1A). Command criteria maybe based on the inclusion of certain keywords within the voice input,among other possibilities. Additionally, or alternately, commandcriteria for commands may involve identification of one or morecontrol-state and/or zone-state variables in conjunction withidentification of one or more particular commands. Control-statevariables may include, for example, indicators identifying a level ofvolume, a queue associated with one or more devices, and playback state,such as whether devices are playing a queue, paused, etc. Zone-statevariables may include, for example, indicators identifying which, ifany, zone players are grouped.

To determine the intent of the words, the VAS is typically incommunication with one or more databases associated with the VAS (notshown) and/or one or more databases (not shown) of the MPS 100. Suchdatabases may store various user data, analytics, catalogs, and otherinformation for natural language processing and/or other processing. Insome implementations, such databases may be updated for adaptivelearning and feedback for a neural network based on voice-inputprocessing. In some cases, the voice utterance portion 680 b may includeadditional information, such as detected pauses (e.g., periods ofnon-speech) between words spoken by a user, as shown in FIG. 6. Thepauses may demarcate the locations of separate commands, keywords, orother information spoke by the user within the voice utterance portion680 b.

After processing the voice input, the VAS may send a response to the MPS100 with an instruction to perform one or more actions based on anintent it determined from the voice input. For example, based on thevoice input, the VAS may direct the MPS 100 to initiate playback on oneor more of the playback devices 102, control one or more of thesedevices (e.g., raise/lower volume, group/ungroup devices, etc.), turnon/off certain smart devices, among other actions. After receiving theresponse from the VAS, the wake-word engine 570 of the NMD 503 (FIG. 5)may resume or continue to monitor the sound-data stream S_(DS) until itspots another potential wake-word, as discussed above.

NMD 503 may also include a local arbitrator 576. Local arbitrator 576may configure the NMD 503 to take various roles, such anarbitrator-related role. In an implementation, local arbitrator 576 mayconfigure an NMD to be either an arbitrator or a non-arbitrator. If theNMD is configured to be an arbitrator, the NMD may perform some or allarbitration functions related to selecting a particular NMD amongstmultiple NMDs (including itself) as the device from which VAS responseswill be output and the source device from which sound data will beextracted, for instance based on determining that the particular NMDidentified a given wake word with the highest confidence level. If theNMD is not configured to be a non-arbitrator, the NMD may be configurednot to perform the function of arbitration, and to defer the function ofperforming arbitration to a local device that is designated as anarbitrator and/or to a remote network device, such as a VAS that isconfigured to perform arbitration. Local arbitrator 576 may designate anNMD as an arbitrator or non-arbitrator in various manners, for instancebased on the NMD's role, based on a selection by a user, etc.

Local arbitrator 576 may determine whether to designate an NMD as anarbitrator or non-arbitrator based on receiving one or more messages,such as UPnP eventing messages, as one example. Local arbitrator 576 maydetermine whether to designate an NMD as an arbitrator or non-arbitratorin various other manners as well.

Returning to FIG. 5, in general, the one or more identificationalgorithms that a particular wake-word engine, such as the wake-wordengine 570, applies are configured to analyze certain characteristics ofthe detected sound stream S_(DS) and compare those characteristics tocorresponding characteristics of the particular wake-word engine's oneor more particular wake words. For example, a particular wake-wordengine 570 may apply one or more identification algorithms to spotspectral characteristics in the detected sound stream S_(DS) that matchthe spectral characteristics of the engine's one or more wake words, andthereby determine that the detected sound S_(D) comprises a voice inputincluding a particular wake word.

In some implementations, the one or more identification algorithms maybe third-party identification algorithms (i.e., developed by a companyother than the company that provides the NMD 103). For instance,operators of a voice service (e.g., AMAZON) may make their respectivealgorithms (e.g., identification algorithms corresponding to AMAZON'sALEXA) available for use in third-party devices (e.g., NMDs 103), whichare then trained to identify one or more wake words for the particularvoice service. Additionally, or alternatively, the one or moreidentification algorithms may be first-party identification algorithmsthat are developed and trained to identify certain wake words that maynot be particular to a given voice service. Other possibilities alsoexist.

In practice, a wake-word engine may include a sensitivity level settingthat is modifiable. The sensitivity level may define a degree ofsimilarity between a word identified in the detected sound stream S_(DS)and the wake-word engine 570's one or more particular wake words that isconsidered to be a match (i.e., that triggers the NMD 103 to invoke thecorresponding VAS). In other words, the sensitivity level defines howclosely, as one example, the spectral characteristics in the detectedsound stream S_(DS) must match the spectral characteristics of theengine's one or more wake words to be a wake-word trigger.

In this respect, the sensitivity level generally controls how many falsepositives that the wake-word engine 570 identifies. For example, if awake-word engine 570 is configured to identify the wake-word “Alexa”with a relatively high sensitivity, then false wake words of “Election”or “Lexus” would cause the wake-word engine 570 to flag the presence ofthe wake-word “Alexa.” On the other hand, if this example wake-wordengine 570 is configured with a relatively low sensitivity, then thefalse wake words of “Election” or “Lexus” would not cause the wake-wordengine 570 to flag the presence of the wake-word “Alexa.”

In practice, a sensitivity level may take a variety of forms. In exampleimplementations, a sensitivity level takes the form of a confidencethreshold that defines a minimum confidence (i.e., probability) levelfor a wake-word engine that serves as a dividing line between triggeringor not triggering a wake-word event when the wake-word engine isanalyzing detected sound for its particular wake word. In this regard, ahigher sensitivity level corresponds to a lower confidence threshold(and more false positives), whereas a lower sensitivity levelcorresponds to a higher confidence threshold (and fewer falsepositives). For example, lowering a wake-word engine's confidencethreshold configures it to trigger a wake-word event when it identifieswords that have a lower likelihood that they are the actual particularwake word, whereas raising the confidence threshold configures theengine to trigger a wake-word event when it identifies words that have ahigher likelihood that they are the actual particular wake word. Otherexamples of sensitivity levels are also possible.

In example implementations, sensitivity level parameters (e.g., therange of sensitivities) for a particular wake-word engine can beupdated, which may occur in a variety of manners. As one possibility, aVAS or other third-party provider of a given wake-word engine mayprovide to the NMD 503 a wake-word engine update that modifies one ormore sensitivity level parameters for the given wake-word engine.

As another possibility, a remote server associated with the MPS 100 mayupdate (or define in the first instance) sensitivity level parametersfor a given wake-word engine, which it may do periodically oraperiodically. In some such cases, the remote server may define orotherwise update sensitivity level parameters for wake-word enginesbased on data regarding characteristics of detected sound (e.g.,spectral and/or gain characteristics) associated with past occurrencesof wake-word triggers (i.e., identifications of the respectiveparticular wake-words for the given engines). In practice, the remoteserver may receive such data from NMDs when wake-word triggers occur orfrom another source of wake-word related sound data (e.g., Internetdatabases or the like). In any case, the remote server may be configuredto perform operations based on such data (e.g., train predictive modelsand/or run simulations) to determine sensitivity parameters for a givenwake-word engine to balance false positives and true identifications ofthe particular wake word.

In example embodiments, a wake-word engine 570 may take a variety offorms. For example, a wake-word 570 may take the form of one or moremodules that are stored in memory of the NMD 503 (e.g., the memory 213;FIG. 2A). As another example, a wake-word engine 570 may take the formof a general-purpose or special-purpose processor, or a module thereof.In this respect, multiple wake-word engines 570 may be part of the samecomponent of the NMD 103 or each wake-word engine may take the form of acomponent that is dedicated for the particular wake-word engine. Otherpossibilities also exist. If a wake-word engine 570 identifies thepresence of a wake word in the detected sound stream S_(D), thewake-word trigger signal S_(W) may be passed to the voice extractor 572to begin extraction for processing voice input, as discussed above.

With reference still to FIG. 5, an NMD may be configured as a playbackdevice that includes the at least one audio interface 519, as discussedabove. The audio interface 519 is generally configured to receive audioin a variety of forms from a variety of sources (e.g., an analog musicsignal or digital data of an Internet podcast). In this regard, theaudio interface 519 may take the form of an analog and/or digitalline-in receptacle that physically connects the NMD 503 to an audiosource and/or may take the form of, or otherwise leverage, the networkinterface 224, that receive audio data via a communication network. Inany case, the audio interface 519 provides an audio stream, A_(S), tothe audio output processing components 515, which in turn process theaudio stream A_(S) prior to the NMD 103 outputting processed audio,A_(P), via the speakers 218. In this respect, the audio outputprocessing components 515 may be the same or similar to the audioprocessing components 218 discussed above.

In some embodiments, one or more of the components described above canoperate in conjunction with the microphones 222 to detect and store auser's voice profile, which may be associated with a user account of theMPS 100. In some embodiments, voice profiles may be stored as and/orcompared to variables stored in a set of command information or datatable. The voice profile may include aspects of the tone or frequency ofa user's voice and/or other unique aspects of the user, such as thosedescribed in previously-referenced U.S. patent application Ser. No.15/438,749.

In some embodiments, one or more of the components described above canoperate in conjunction with the microphones 222 to determine thelocation of a user in the home environment and/or relative to a locationof one or more of the NMDs 103. Techniques for determining the locationor proximity of a user may include one or more techniques disclosed inpreviously-referenced U.S. patent application Ser. No. 15/438,749, U.S.Pat. No. 9,084,058 filed Dec. 29, 2011, and titled “Sound FieldCalibration Using Listener Localization,” and U.S. Pat. No. 8,965,033filed Aug. 31, 2012, and titled “Acoustic Optimization.” Each of theseapplications is herein incorporated by reference in its entirety.

In some embodiments, the MPS 100 is configured to temporarily reduce thevolume of audio content that it is playing while identifying the wakeword portion 610 of a voice input. For instance, the MPS 100 may restorethe volume after processing the voice input 600. Such a process can bereferred to as ducking, examples of which are disclosed inpreviously-referenced U.S. patent application Ser. No. 15/438,749.

III. Example Local Arbitration and Designation of VAS Response Playback

Further examples of local arbitration and designation of a playbackdevice to output a VAS response with will now be described in detail. Asdiscussed above, multiple playback or NMDs devices may combined invarious manners. For example, NMD-equipped playback devices 102 may bebonded to form a “bonded set.” In a bonded set, a playback device mayhave a different playback responsibility than another playback device inthe set. For instance, a first playback device of a bonded set may beresponsible for audio playback of a left audio channel, and a secondplayback device may be responsible for playback of a right audiochannel. An example of such a bonded set is shown and described above inconnection with FIG. 3B. As another example of a bonded set, a thirdplayback device of a bonded set may be responsible for playback of acenter audio channel, such as the front playback device 102 b, such asshown and described above in connection with FIGS. 3C and 3D. In someimplementations, a left channel device (or alternatively a right channeldevice) in a stereo pair may be selected as the arbitrator NMD. In asimilar fashion, one of a left, right, or center channel device may beselected as an arbitrator NMD in a home theater implementation.

In various implementations, implementing an arbitrator NMD in a bondedset may prevent the ping-pong effect. Further, an arbitrator NMD mayconserve bandwidth by reducing the number of NMDs that communicate witha VAS when multiple NMDs identify a same wake word. In addition, oralternatively, an NMD may also be designated as the arbitrator NMD for aset of NMD-equipped playback devices comprising a group of playbackdevices in which none or only some of the playback devices are assigneda playback responsibility.

Turning to the example illustrated in FIG. 3D, front playback device 102b is bonded with SUB playback device 102 k, and right and left playbackdevices 102 a and 102 j, respectively. In the examples now described,the playback devices 102 a, 102 b, and 102 j are NMD-equipped playbackdevices and are referred to as playback devices for purposes of thefollowing discussion. Also, while specific reference is made to FIG. 3Dfor the purpose of illustrating examples of arbitration and VAS responseplayback in the context bonded set, it should be understood that any ofthe techniques described herein may describe any configuration of bondedNMDs, playback zones comprised of multiple NMDs, or other media playbacksystem configurations.

In the context of FIG. 3D, each of the NMD-equipped playback devices 102in FIG. 3D may be configured to detect sound (i.e. audio waves)comprising ambient and/or background noise and which may also comprisespeech intended to be processed by any of NMDs 102 a, 102 b, or 102 j.The detected sound may be input into a voice capturing module, such asVCC 510 where the audio may undergo various types of pre-processing,spatial processing, etc., before buffers, such as buffers 568, and 569capture data corresponding to the detected sound.

In example embodiments, at least one of the playback devices 102 maycomprise a device, such as the arbitrator NMD, which may be the defaultNMD for outputting VAS responses in a set of NMDs. While the arbitratorNMD is described according to various examples as the default NMD foroutputting VAS responses, it should be understood that devices otherthan the arbitrator NMD may also be designated as the default device foroutputting VAS responses.

The arbitrator NMD may also be responsible for selecting which of NMDs102 that is to extract detected-sound data for evaluation by a VAS. Insome examples, the arbitrator NMD may be an NMD that has a greateramount of computational resources (e.g., processing power, memory,storage, etc.). In some examples, a device other than the arbitrator NMDmay be configured to extract the detected-sound data.

For example, in some implementations, the arbitrator NMD may be assignedduring the configuration of the media playback system that includes thetwo or more NMDs, which may be arranged as a bonded set. According to animplementation, UPnP eventing may be used to set the value of a stateindicator that specifies the identity of the arbitrator NMD to a VASand/or to other playback devices on a same network as the arbitratorNMD. A user may also manually specify the arbitrator NMD during theconfiguration of the media playback system. In some cases, thearbitrator responsibilities may be assigned to a given NMD in the setbased on the NMD's role or hardware resources.

In some implementations, the arbitrator responsibilities may be assignedto a given NMD based on other considerations. For instance, thearbitrator responsibilities may be assigned to an NMD that has alreadybeen assigned other responsibilities within the media playback system.As one example, an NMD designated as the “group coordinator” that isresponsible for facilitating synchronous playback of audio among the twoor more NMDs may be assigned arbitrator responsibilities as well. Asanother example, an NMD designated as the “primary” device that isresponsible for playing back a given audio channel, such as the centerchannel (e.g., playback device 102 j) of a home theatre setup or eitherthe left channel of a stereo pair setup, may also be assigned thearbitrator responsibilities.

In any case, in accordance with example embodiments provided herein,local arbitration may generally involve two or more NMD-equippedplayback devices (e.g., NMD-equipped playback devices 102 a, 102 b, and102 j) of the media playback system identifying a particular wake word,the arbitrator NMD (e.g., NMD-equipped playback device 102 b) selectingone of the NMD-equipped playback devices to extract detected-sound datathat may include a voice input for evaluation by the VAS, and afterevaluation of the detected-sound data by the VAS, the arbitrator NMDplaying back a VAS response indicated by VAS response data generated bythe VAS.

More specifically, in an example implementation, each non-arbitratordevice (e.g., NMD-equipped playback devices 102 b and 102 j) NMD thatidentifies a particular wake word may transmit to the arbitrator NMD anotification that a wake word was identified. In some examples, a givennotification may include a confidence level that the givennon-arbitrator NMD identified the particular wake word correctly. In thecase that an identifying NMD is the arbitrator NMD, the arbitrator NMDmay not transmit a message that includes a confidence level but insteadmay generate an internal notification, which may include a confidencelevel that the arbitrator NMD identified the wake word correctly.

In practice, a confidence level may take various forms. For example, theconfidence level may be metadata such as a metric calculated based onaudio properties of the received wake word. Examples of some suchmetrics that may be used to calculate the confidence level may include asignal-to-noise ratio (SnR), a frequency spectrum of the identified wakeword, a direction of the identified wake word, an amplitude (e.g.,decibel level) of the identified wake word, etc. A confidence level maytake various other forms as well.

In turn, the NMD-equipped playback device comprising the arbitrator NMDreceives each of the notifications. Based on these notificationsreceived, the arbitrator NMD may determine that more than one of theNMD-equipped playback devices 102 has identified the wake word at thesame time. In response to this determination, the arbitrator NMD maynext select which of the identifying NMDs is to extract thedetected-sound data that may include a voice input for evaluation by theVAS. The arbitrator NMD may make this selection in various manners.

As one example, if the notifications include respective confidencelevels in their identification of the wake word, the arbitrator NMD mayselect the NMD having the highest confidence level. For instance, if theNMD-equipped playback device 102 a identifies the wake word with ahigher confidence level than the arbitrator NMD, the arbitrator NMD mayselect that playback device over all other playback devices of the set.As another example, if the NMDs have differing roles, the arbitrator NMD102 b may use these roles as a basis for selecting which of the NMDs isto extract detected-sound data. For instance, if the NMD of NMD-equippedplayback device 102 j has a group coordinator role in the bonded set inFIG. 3D, the arbitrator NMD may select NMD 102 j. Other examples ofselecting the extraction NMD are also possible.

After selecting an NMD to extract the detected-sound data, thearbitrator NMD may cause the selected NMD to extract the detected-sounddata that may include the voice input for evaluation by the VAS. In thisrespect, it should be understood that the extraction NMD may differfrom, or be the same as, the arbitrator NMD that is designated to outputa voice output. The process of causing the selected NMD to extract thedetected-sound data may take various forms.

As one example, if the arbitrator NMD selects a non-arbitrator NMD suchas the NMD-equipped playback device 102 b, then the arbitrator NMD maysend an instruction to this non-arbitrator NMD to extract thedetected-sound data that may include a voice input for evaluation by theappropriate VAS. As another example, if the arbitrator NMD selectsitself for extraction, then the arbitrator NMD 102 b may trigger itsinternal voice capture components (e.g., VCC 510) to extract thedetected-sound data for evaluation by the VAS.

After extracting the detected-sound data, the selected NMD may formatthe detected-sound data into a sound-data stream and transmit thesound-data stream containing at least the detected-voice data that mayinclude a voice input (and perhaps also the wake word) to the VAS eitherdirectly via a communication network that couples the VAS and the mediaplayback system or indirectly via the arbitrator NMD. In this respect,only one NMD or NMD-equipped playback device transmits a sound-datastream to the VAS, which consumes significantly less bandwidth than whenmultiple devices make such transmission.

After receiving the voice utterance of the voice input, the VAS maygenerate a VAS response that is based at least on the voice utterance ofthe voice input. In this regard, the VAS advantageously only has toprocess a single sound-data stream from the media playback system anddoes not need to perform analyses related to remote arbitration, whichmay help to conserve the VAS′ compute resources.

Thereafter, the VAS may determine the identity of the arbitrator NMD 102b and send to the arbitrator NMD 102 b a message including, or otherwiseindicating, the VAS response via the communication network.

The VAS may determine the identity of the arbitrator NMD 102 b invarious different manners. According to an embodiment, the VAS mayidentify the arbitrator NMD 102 b via UPNP. As one example, UPNPeventing may be used to set the value of a state indicator thatspecifies the identity of the arbitrator NMD 102 b to the VAS. Inpractice, the group coordinator of a bonded set may be the arbitratorNMD. The VAS may determine the identity of the arbitrator NMD in variousother manners as well.

After receiving the VAS response message, the arbitrator NMD outputs theVAS response. In this way, the media playback system exhibits a morepredictable behavior that aligns with users' expectations. Outputtingthe VAS response may comprise playing back spoken words, audible tones,and/or various other forms of audio played back in response to a voiceinput. Outputting the VAS response may also take the form of outputtingvarious visual signals such as one or more lights, outputting graphicson a display, etc. Some of these VAS responses may indicate whether theVAS and/or the NMD will perform a given action (e.g., begin musicplayback, output requested information, etc.) specified by the voiceutterance of the voice input. VAS responses may take various other formsas well.

In line with the above discussion, and with reference to FIG. 5, theplayback device 102 a configured with components and functionality of anNMD 103 may include an audio output interface 530, a network interface230, at least one processor (e.g. VCC 510, wake-word engine 520, etc.),and at least one microphone 224 each which is configured to detectsound.

IV. Example Use Cases

Turning now to FIG. 7A, a conceptual diagram of an example set ofNMD-equipped playback devices of a network system configured inaccordance with aspects of this disclosure is depicted. The exampledepicted in FIG. 7A depicts a use case in a network media playbacksystem is configured to perform localized arbitration and has adesignated arbitrator NMD for at least a subset of playback devices ofthe media playback system.

The network media playback system depicted in FIG. 7A includes the rightplayback device 102 a, the front playback device 102 b, and the leftplayback device 102 j, which may be collectively referred to as“playback devices 102.” While playback devices 102 are described asbeing playback devices, some or all of playback devices 102 may also beor may include NMDs. In the network media playback system depicted inFIG. 7A, front playback device 102 b is designated as the arbitratorNMD.

An example behavior of a set of NMD-equipped playback devices of a mediaplayback system in response to a user speaking a voice input comprisinga voice input comprising a wake word and a voice utterance will now bedescribed in greater detail. In the illustrated example of FIG. 7A, thefront playback device 102 b is the arbitrator NMD.

In the example of FIG. 7A, the user speaks a wake word, such as “HeySonos,” or another suitable wake word, such as “Hey Google” or “Alexa”which some or all of playback devices 102 may have detected. The wakeword may have been followed by the voice utterance “Turn on the TV”(event “i”). In the illustrated example of FIG. 7A, the front playbackdevice 102 b outputs a confirmation, such as by playing a chime (event“ii”), indicating that the voice input was detected. In one aspect, thefront playback device 102 b is the only playback device in the set ofplayback devices 102 that plays the chime, including cases in which thefront playback device 102 b itself did not detect the voice input. Inthis example, each of the playback devices that detected the given wakeword begin performing local extraction by sending data including aconfidence level and sound-stream data captured by a given playbackdevice to the arbitrator NMD, which is the front playback device 102 b.

After receiving the confidence levels from each of the playback devices,the front playback device 102 b selects the playback device whichidentified the given wake word with the highest confidence level, theright playback device 102 a in this example, to perform localextraction. In some examples, the right playback device 102 a may sendinstructions to cause the non-selected playback device 102 j to ceaseperforming local extraction. Playback device 102 b may send aninstruction to cause left playback device 102 a to perform localextraction.

In any case, after selecting the right playback device 102 a to performlocal extraction, the front playback device 102 b sends the extractedsound-data stream received from the right playback device 102 a to aremote network device, such as VAS 190, which in turn determines theintent of the voice input included in the sound-data stream and sendsvoice output response data back to the arbitrator NMD, which is thefront playback device 102 b in this example.

In turn, the front playback device 102 b generates a voice outputresponse which may take the form of an audio or visual response based onthe voice output response data received from VAS 190. In the example ofFIG. 7A, the VAS response may take the form of an audio response, suchas the word “Okay” (event “iii”). Finally, the arbitrator NMD, the frontplayback device 102 b, outputs the VAS response via a speaker componentof the front playback device 102 b

Turning now to FIG. 7B, another conceptual diagram of an example set ofNMD-equipped playback devices of a network system configured inaccordance with aspects of this disclosure is depicted. The exampledepicted in FIG. 7B depicts a use case in which network media playbacksystem is configured to perform localized arbitration and has adesignated arbitrator NMD.

The network media playback system depicted in FIG. 7B includes the sameplayback devices 102 as illustrated in FIG. 7A. In the network mediaplayback system depicted in FIG. 7B, the front playback device 102 b maybe designated as the arbitrator NMD. An example behavior of the mediaplayback system depicted in FIG. 7B in response to a user speaking avoice input comprising a voice input comprising a wake word and a voiceutterance will now be described.

In the example depicted in FIG. 7B, the user speaks a wake word, “HeySonos,” or other suitable wake word, such as “Hey Google” or “Alexa”which some or all of playback devices 102 may have detected, followed bythe voice utterance “Play the Beatles” (event “iv”). In this example,each of the playback devices that detected the given wake word beginperforming local extraction by sending data including a confidence leveland extracted sound-stream data captured by a given playback device tothe arbitrator device, which is the front playback device 102 b. Thefront playback device 102 b may also play a chime (not shown) asdescribed above, indicating that the voice input was detected.

After receiving the confidence levels from each of the playback devices,the front playback device 102 b selects the playback device whichdetected the given wake word with the highest confidence level, which isthe front playback device 102 b itself in this example, to perform localextraction. In some examples, in addition to selecting itself to performlocal extraction, the front playback device 102 b may send instructionsto cause non-selected playback devices 102 a and 102 j to ceaseperforming local extraction.

In any case, after the front playback device 102 b selects itself toperform local extraction, the front playback device 102 b sends thesound-data stream extracted locally to a remote network device, such asVAS 190, which in turn determines the intent of the voice input includedin the sound-data stream and sends VAS response data back to thearbitrator device, which is the front the playback device 102 b.

In turn, the front playback device 102 b generates a VAS response whichmay take the form of an audio or visual response based on the VASresponse data received from VAS 190. In the example of FIG. 7B, thegenerated VAS may take a form of spoken audio such as “Would you like tocreate a Beatles station?” (event “v”). Finally, the arbitrator device,front playback device 102 b, outputs the VAS response via speakers ofthe front playback device 102 b.

Turning now to FIGS. 8A and 8B, example message flow diagrams forperforming local arbitration between two or more playback devices inaccordance with this disclosure are depicted. The message flow diagramsmay correspond to implementations shown in one or both of FIGS. 7A and7B. At a high level, FIG. 8A depicts a flow of data among NMD-equippedplayback devices 102 a, 102 b, 102 j, and a remote device 106 a in whichplayback device 102 b is the arbitrator NMD.

To begin the flow illustrated in FIG. 8A, each of playback devices 102a, and 102 j may identify wake words 802 and 804, respectively. Alsooptionally, at block 800, the playback device 102 b may also identify asame wake word as the playback devices 102 a and 102 j. Afteridentifying wake words 802 and 804, at block 806, the playback device102 a may perform local extraction by sending sound features that arerelated to identifying the given wake word, and may be used to determinea confidence level, as well as an extracted sound-data stream to theplayback device 102 b. At block 808, the playback device 102 j may alsoperform local extraction by sending metadata related to identifying thegiven wake word, such as a confidence level, as well as an extractedsound-data stream to the playback device 102 b.

Next, at block 810, the playback device 102 b may compare sound features(e.g., as part of performing arbitration), such as confidence levelsincluded in the sound features received from the playback device 102 aand the playback device 102 j and may select the playback device thatdetected the given wake word with the highest confidence level, which inthis example is playback device 102 a.

In some examples, after selecting a playback device, the arbitrator NMD,in this case playback device 102 b, may output a confirmation 812 toindicate to any users that playback device 102 b is designated as thearbitrator NMD and as such users should expect playback device 102 b togenerate and output any VAS responses. Outputting a VAS response takevarious forms. As an example, the VAS response may take the form of anaudio indication (e.g., a voice response) and/or visual indication thatplayback device 102 b may output. Outputting a VAS response may takevarious other forms as well.

At block 814, the playback device 102 b may transmit the extracted sounddata, (e.g., an extracted sound-data stream) received from the selectedplayback device 102 a to the remote device 106 a. At block 816, theremote device 106 a, which may comprise a VAS, may process the voiceinput included in the extracted sound data 814 received from playbackdevice 102 b.

At block 818, the playback device 102 b may transmit an instruction tocause playback device 102 j to stop local extraction 818 due to theplayback device 102 b selecting playback device 102 a to perform localextraction rather than playback device 102 j. While block 818 isillustrated as occurring after block 814 and block 816, block 818 mayoccur before or between either of these blocks as well.

At block 820, after receiving sufficient extracted sound data to processthe voice input, remote device 106 a may transmit message 820 to causethe playback device 102 b to stop extraction. Playback device 102 b may,in turn, send a message to the selected playback device 102 a to causethe playback device 102 a to stop performing local extraction (notpictured for the sake of clarity).

At block 822, the playback device 102 b may receive VAS response data,and based on the received VAS response data, the playback device 102 bmay process (block 824) a VAS response, which may comprise outputting aVAS response, based on the received VAS response data.

Turning now to FIG. 8B, another example message flow diagram ofperforming arbitration between two or more playback devices inaccordance with this disclosure is depicted. At a high level, FIG. 8Bdepicts a flow of data among the playback devices 102 a, 102 b, 102 j,and the remote device 106 a in which the playback device 102 b is anarbitrator NMD.

To begin the flow illustrated in FIG. 8B, at blocks 802 and 804, each ofthe playback devices 102 a, and 102 j may identify wake words. Alsooptionally, at block 800, the playback device 102 b may also identify asame wake word as the playback devices 102 a and 102 j. Then, at block832, after identifying the respective wake words at block 802 and 804,the playback device 102 a may send a first sound feature of the firstwake word by sending metadata related to identifying the given wakeword, such as a confidence level, to the playback device 102 b. At block834, the playback device 102 j may send a second sound feature bysending metadata related to identifying the given wake word, such as aconfidence level, to the playback device 102 b.

Next, at block 810, the playback device 102 b may compare soundfeatures, such as the received confidence levels included in the firstand second sound features received from the playback device 102 a andthe playback device 102 j, and optionally sound features detected by theplayback device 102 b itself, and may select the playback device thatdetected the given wake word with the highest confidence level, whichmay be the playback device 102 j in the example of FIG. 8B.

In some examples, at block 812, after selecting a playback device, thearbitrator NMD, in this case the playback device 102 b, may output aconfirmation to indicate to any users that the playback device 102 b isdesignated as the arbitrator NMD and as such, users should expect theplayback device 102 b to generate and output any VAS outputs. Outputtinga confirmation may take various forms. As an example, the outputconfirmation may take the form of an audio indication (e.g., a voiceresponse) and/or visual indication that the playback device 102 b mayoutput.

At block 842, the playback device 102 b may transmit an instruction tocause the selected playback device 102 j to begin performing extraction.In turn, at block 844, the playback device 102 j may transmit extractedsound data, which may take the form of a sound-data stream, to theremote device 106 a.

After the remote device 106 a receives the extracted sound data, theremote device 106 a may process the voice input 816 included in theextracted sound data received from the playback device 102 j. Then, atblock 846, after receiving sufficient extracted sound data to processthe voice input, the remote device 106 a may transmit a message to causethe playback device 102 j to stop extraction.

Then, at block 852, remote device 106 a may send a VAS response to theplayback device 102 j. Playback device 102 j, in turn, transmits the VASresponse data to the playback device 102 b (block 854), which isdesignated as the arbitrator.

At block 856, the playback device 102 b may receive VAS response data,and based on the received VAS response data, the playback device 102 bmay process (block 856) a VAS response, such as outputting a voiceresponse, based on the received VAS response data.

In various implementations, the arbitrator NMD may also identify wakewords as shown at block 800 in FIGS. 8A and 8B. In cases in which thearbitrator NMD determines that it has identified a wake word with thehighest confidence level among one or more NMDs in a set, the arbitratorNMD may trigger its internal voice capture components to extract thedetected-sound data for evaluation of a voice input by the VAS, whileany of the other NMD(s) that were not selected do not extract theirrespective detected-sound data, such as in the manner described above.

In some implementations, NMDs and/or NMD-equipped playback devices mayinteract with one or more remote servers for remote arbitration betweensets of devices (e.g., between two arbitrator NMDs of different sets ofNMD-equipped playback devices) and/or between a set of devices and oneor more NMDs that are not part of the set. In any case, each NMD that isconfigured to interact with the remote VAS for such arbitration maydetect sound, capture detected-sound data in a respective buffer,identify the same wake word, and extract the detected-sound data thatmay include a voice input from the respective buffer. They may then sendtheir respective extracted detected-sound data and voice inputs in theform of a detected-sound data stream to a VAS that determines which oneNMD identified the wake word with a higher level of confidence.

Referring to FIG. 9A, another conceptual diagram of an example set ofNMD-equipped playback devices of a network system configured inaccordance with aspects of this disclosure is depicted. The example ofFIG. 9A depicts a use case in a which network media playback system isconfigured to perform local arbitration for a bonded set that has adesignated arbitrator NMD, and a VAS may be configured to performsubsequent remote arbitration between the local arbitrator NMD and theplayback device 102 e that is not part of bonded the set associated withthe arbitrator NMD.

The network media playback system depicted in FIG. 9A includes a bondedset comprising playback devices 102 a, 102 b, and 102 j. The networkmedia playback system also includes the NMD-equipped playback device 102e that belongs to a “bedroom” zone group and that is not part of the setcomprising the playback devices 102 a, 102 b, and 102 j. The frontplayback device 102 b may be designated as the arbitrator NMD for thebonded set, and a VAS may be configured to arbitrate between theplayback device 102 e belonging to the zone group and the bonded setcomprising the playback devices 102 a, 102 b, and 102 j.

An example behavior of media playback system in response to a userspeaking a voice input comprising a voice input comprising a wake wordand a voice utterance will now be described. In the example of FIG. 9A,the user speaks a wake word, “Hey Sonos,” or other suitable wake word,such as “Hey Google” or “Alexa” which some or all of the playbackdevices 102 may have identified. The followed by the voice utterance“Turn off the TV” (event “vi”). In this example, each of the playbackdevices in the bonded set that identified the given wake word beginperforming local extraction by sending data including a confidence leveland sound-stream data captured by a given playback device to thearbitrator NMD, which is the front the playback device 102 b.

After receiving the confidence levels from each of the playback devices,the front playback device 102 b selects the playback device whichdetected the given wake word with the highest confidence level. As anexample, the left playback device 102 a may have detected the given wakeword with the highest level, and consequently the front playback device102 b may select the left playback device 102 j to perform localextraction for the bonded set and may transmit an extracted sound-datastream from the selected left playback device 102 j to the VAS forarbitration and voice processing. In some examples, as a result ofselecting the left playback device 102 a to perform local extraction,the front playback device 102 b may send instructions to cause thenon-selected playback device 102 j and itself, to cause them to ceaseperforming local extraction.

In addition to the local arbitration performed by the bonded set, theplayback device 102 e from the Bedroom zone group also detects the givenwake word and may perform extraction by sending data indicating aconfidence level determined associated with the identifying the givenwake word and sound-stream data captured by the playback device 102 e toa VAS for arbitration and voice processing.

After the VAS receives the confidence levels from the selected playbackdevices, namely the playback device 102 e of the Bedroom zone group andthe left playback device 102 j, the VAS performs arbitration byselecting the playback device from the Bedroom zone group or the bondedset that detects the given wake word with the highest confidence level.In this example, the playback device 102 e of the Bedroom zone groupdetects the given wake word with the highest confidence level.

After selecting the playback device 102 e, VAS 190 determines the intentof the voice input included in the extracted sound-data stream receivedfrom the playback device 102 e and also sends voice output response databack to the selected device, which is the playback device 102 e in thisexample. In some examples, VAS 190 may also send an instruction to causethe device a non-selected device, such as the left playback device 102 jor the front playback device 102 b and/or not to output a VAS response.

After the selected playback device 102 e receives the voice output data,playback device 102 e generates a VAS response which may take the formof an audio or visual response based on the voice output response datareceived from VAS 190. In the example of FIG. 9A, the generated voiceoutput response may take the form of a VAS response such as “Okay”(event “vii”). Finally, the arbitrator NMD, the playback device 102 e ofthe Zone group, an audio interface of the playback device 102 e outputsa voice output response via speakers of the playback device 102 e.

Turning now to FIG. 9B, another example message flow of performing localarbitration between two or more playback devices followed by remotearbitration with one or more additional playback devices in accordancewith this disclosure is depicted. At a high level, FIG. 9B depicts anextracted sound stream provided to the remote device 106 a. FIG. 9B maybe one example among others of messages exchanged during theimplementation depicted in FIG. 9A.

To begin the flow illustrated in FIG. 9B, at block 902 the playbackdevice 102 e identifies a wake word. Additionally, one or more of theplayback devices 102 a, 102 b, and 102 j (not shown) has identified thewake word, and the local arbitrator of that set of devices may initiateextraction, such as in a manner described above. For example, theplayback device 102 a may perform local extraction by sending extractedsound data to playback device 102 b, which ultimately extracts thedetected sound data to the remote VAS, as shown at block 908.

At block 960, and after identifying the wake word at block 902, theplayback device 102 e may also output a confirmation, which may besimilar to the confirmation output by the playback device 102 b. Atblock 962, the playback device 102 e may transmit its ownlocally-extracted sound data, which may take the form of metadata thatmay include sound features that may define a confidence level, as wellas an extracted sound-data stream, to the remote device 106 a forarbitration.

At block 964, after receiving extracted sound data from the playbackdevice 102 e and the bonded set of playback devices, the remote device106 a may processes the received extracted sound data. Processing theextracted sound data further includes processing the voice inputincluded in the extracted sound data received from the playback device102 b that identified the given wake word with the highest confidencelevel. Additionally, block 964 may include the remote device 106 aperforming arbitration between the playback device 102 e and thearbitrator NMD (the NMD-equipped playback device 102 b, not pictured) ofthe bonded set of playback devices. More particularly in the example ofFIG. 9B, to perform arbitration, the remote device 106 a may select theplayback device from either the zone group that includes the playbackdevice 102 e or the bonded set that includes the playback devices 102 a,102 b, and 102 j that identified the given wake word with the highestconfidence level, which in this example is the playback device 102 e.Upon selecting the playback device 102 e, the remote device 106 a maysend an instruction to stop extraction from non-selected device(s), suchas shown at block 966, upon the remote device 106 a selecting theplayback device 102 e over the set of the playback devices 102 a, 102 b,and 102 j.

At block 968, after receiving sufficient extracted sound data to processthe voice input, the remote device 106 a may transmit a message to causethe playback device 102 e to stop extraction. Then, at block 970, remotedevice 106 a may send VAS response data to the playback device 102 e.

Finally, at block 972, the playback device 102 e may receive the VASresponse data, and based on the received VAS response data, may process(e.g., output) a VAS response based on the received VAS response data.

As another example, if the remote device 106 a determines that thebonded set of playback devices detected the wake word with a higherconfidence level than the playback device 102 e, the remote device 106 acan process extracted sound data that it receives from the bonded set(and cease extraction from the playback device 102 e). The remote device106 a can then provide a VAS response to the arbitrator NMD, asdescribed above.

V. Example Local Arbitration and Output Designation Flow Diagram

For purposes of illustration only, an example method 1000 for locallyarbitrating between two or more playback devices in accordance with thisdisclosure is depicted in FIG. 10 and discussed below as being carriedout by a playback device of the MPS 100 that is configured with adesignated arbitrator NMD, such as one of the right or left playbackdevices of FIG. 3B or one of the right, left, or front playback devicesof FIG. 3D. However, it should be understood that the method 1000 ismerely exemplary. For instance, one or more blocks shown in the flowdiagram of FIG. 10 may be rearranged into different orders, combinedinto fewer blocks, separated into additional blocks, and/or removedaltogether. It should further be understood that the method 1000 couldbe performed by a device other than a playback device of the MPS 100,which may be part of a different type of system.

Turning now to FIG. 10, at block 1002, a first playback device equippedwith an arbitrator NMD may detect sound via the at least one microphone222.

At block 1004, the first playback device may identify a wake word basedon the detected sound. The first playback device may identify the wakeword based on the detected sound from a notification generated by theplayback device or received from a second playback device, i.e., anon-arbitrating playback device.

At block 1006, the first playback device may receive, via the networkinterface 224, an indication that the second playback device, which maybe in a bonded set or group with the first playback device, has alsodetected the sound and identified the wake word based on the sound asdetected by the other playback device

At block 1008, after receiving the indication, the first playback devicemay evaluate which of the playback devices in a set or group of devicesis to extract sound data representing the sound. In the illustratedexampled depicted in FIG. 10, the first playback devices determines thatthe extraction of the sound data is to be performed by the secondplayback device over the first playback device.

At block 1010, in response to determining that the second playbackdevice is to extract the sound data, the first playback device mayforego extraction of the sound data at the first playback device. Insome embodiments, the first playback device may then forward theextracted sound data of the second playback device to the VAS, while inother embodiments, the second playback device may directly transmit theextracted sound data to the VAS without forwarding the sound data to thefirst playback device, as discussed above.

At block 1012, the first playback device may receive, via the networkinterface 224 and from a network-based system configured to evaluatesound data for voice input and determine a corresponding VAS response(e.g., VAS 190), VAS response data that is indicative of a given VASresponse corresponding to a given voice input identified in the sounddata extracted by the second playback device.

Then, at block 1014, based on the VAS response data, the first playbackdevice may output the given VAS response via one or more interfaces,such audio output interface 519, a visual interface or in various othermanners.

CONCLUSION

The description above discloses, among other things, various examplesystems, methods, apparatus, and articles of manufacture including,among other components, firmware and/or software executed on hardware.It is understood that such examples are merely illustrative and shouldnot be considered as limiting. For example, it is contemplated that anyor all of the firmware, hardware, and/or software aspects or componentscan be embodied exclusively in hardware, exclusively in software,exclusively in firmware, or in any combination of hardware, software,and/or firmware. Accordingly, the examples provided are not the onlyway(s) to implement such systems, methods, apparatus, and/or articles ofmanufacture.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.For example, in some implementations the arbitrator NMD may beconfigured to disregard some or all other NMDs in a set of bondeddevices, such as by disabling wake-word detection on some or all of theNMDs in the set (e.g., to mitigate or further mitigate a ping-pongeffect). In other instances, well known methods, procedures, components,and circuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible,non-transitory medium such as a memory, DVD, CD, Blu-ray, and so on,storing the software and/or firmware.

The present technology is illustrated, for example, according to variousaspects described below. Various examples of aspects of the presenttechnology are described as numbered examples (1, 2, 3, etc.) forconvenience. These are provided as examples and do not limit the presenttechnology. It is noted that any of the dependent examples may becombined in any combination, and placed into a respective independentexample. The other examples can be presented in a similar manner.

Example 1: A computer-implemented method comprising: detecting sound viaat least one microphone, identifying a wake word based on the sound asdetected by a first playback device, receiving, via a network interface,an indication that a second playback device has also detected the soundand identified the wake word based on the sound as detected by thesecond playback device, after receiving the indication, evaluating whichof the first and second playback devices is to extract sound datarepresenting the sound and thereby determining that the extraction ofthe sound data is to be performed by the second playback device over thefirst playback device, in response to the determining, foregoingextraction of the sound data at the first playback device, receiving,via the network interface from a network-based system that is configuredto evaluate sound data for voice input and determine a corresponding VAS(Voice Assistant Service) response, VAS response data that is indicativeof a given VAS response corresponding to a given voice input identifiedin the sound data extracted by the second playback device, and based onthe VAS response data, playing back the given VAS response via an audiooutput interface.

Example 2: the computer-implemented method of claim 1, whereinidentifying the wake word based on the sound as detected by the firstplayback device triggers the first playback device to determine a firstfeature of the sound as detected by the first playback device, whereinthe indication that the second playback device has also detected thesound and identified the wake word based on the sound as detected by thesecond playback device comprises an indication of a second feature ofthe sound as detected by the second playback device, and whereinevaluating which of the first and second playback devices is to extractthe sound data comprises comparing the first feature to the secondfeature.

Example 3: the computer-implemented method of any combination ofExamples 1-2, wherein the first feature comprises a firstsignal-to-noise ratio of the sound as detected by the first playbackdevice, and wherein the second feature comprises a secondsignal-to-noise ratio of the sound as detected by the second playbackdevice.

Example 4: The computer-implemented method of any combination ofExamples 1-3, in response to the determining, instructing the secondplayback device to perform the extraction of the sound data.

Example 5: The computer-implemented method of any combination ofExamples 1-4, wherein the extraction of the sound data involvestransmission of the sound data to the network-based system.

Example 6: The computer-implemented method of any combination ofExamples 1-5, further comprising: receiving the sound data from thesecond playback device via the network interface, and transmitting thereceived sound data to the network-based system via the networkinterface.

Example 7: The computer-implemented method of any combination ofExamples 1-6, further comprising: detecting a second sound via the atleast one microphone, identifying the wake word based on the secondsound as detected by the first playback device, receiving, via thenetwork interface, a second indication that the second playback devicehas also detected the second sound and identified the wake word based onthe second sound as detected by the second playback device, afterreceiving the second indication, evaluating which of the first andsecond playback devices is to extract second sound data representing thesecond sound and thereby determining that the extraction of the secondsound data is to be performed by the first playback device over thesecond playback device, begin to perform the extraction of the secondsound data, and thereafter cease the extraction of the second sound datain response to receiving an indication that the network-based system hasselected a third playback device to extract the second sound data.

Example 8: The computer-implemented method of any combination ofexamples 1-7, wherein the first playback device and the second playbackdevice are members of a bonded set, and wherein the third playbackdevice is not a member of the bonded set.

Example 9: The computer-implemented method of any combination ofexamples 1-8, wherein the VAS response data comprises at least one of(a) a data representation of the given VAS response or (b) an identifierof the given VAS response.

Example 10: A first playback device, comprising: at least onemicrophone, an audio output interface, a network interface, at least oneprocessor, a non-transitory computer-readable medium; and programinstructions stored on the non-transitory computer-readable medium that,when executed by the at least one processor, cause the first playbackdevice to perform functions comprising: any combination of Examples 1-9.

Example 11: A tangible, non-transitory, computer-readable medium havinginstructions stored thereon that are executable by one or moreprocessors to cause a first playback device to perform operationscomprising: any combination of Examples 1-10.

The invention claimed is:
 1. A first playback device of a local playbacknetwork comprising: at least one microphone; an audio output interface;a network interface; at least one processor; a non-transitorycomputer-readable medium; and program instructions stored on thenon-transitory computer-readable medium that, when executed by the atleast one processor, cause the first playback device to performfunctions comprising: detecting sound via the at least one microphone;identifying a wake word based on the sound as detected by the firstplayback device; receiving, via the network interface, an indicationthat a second playback device of the local playback network has alsodetected the sound and identified the wake word based on the sound asdetected by the second playback device; after receiving the indication,evaluating which of the first and second playback devices is to extractsound data representing the sound and thereby determining that theextraction of the sound data is to be performed by the second playbackdevice over the first playback device; based on determining that theextraction of the sound data is to be performed by the second playbackdevice over the first playback device, (i) causing the second playbackdevice to proceed with extraction of the sound data and (ii) foregoingextraction of the sound data at the first playback device; receiving,via the network interface from a network-based system that is configuredto evaluate sound data for voice input and determine a corresponding VAS(Voice Assistant Service) response, VAS response data that is indicativeof a given VAS response corresponding to a given voice input identifiedin the sound data extracted by the second playback device; and based onthe VAS response data, outputting the given VAS response via an audiooutput interface of the first playback device.
 2. The first playbackdevice of claim 1, wherein identifying the wake word based on the soundas detected by the first playback device triggers the first playbackdevice to determine a first feature of the sound as detected by thefirst playback device, wherein the indication that the second playbackdevice has also detected the sound and identified the wake word based onthe sound as detected by the second playback device comprises anindication of a second feature of the sound as detected by the secondplayback device, and wherein evaluating which of the first and secondplayback devices is to extract the sound data comprises comparing thefirst feature to the second feature.
 3. The first playback device ofclaim 2, wherein the first feature comprises a first signal-to-noiseratio of the sound as detected by the first playback device, and whereinthe second feature comprises a second signal-to-noise ratio of the soundas detected by the second playback device.
 4. The first playback deviceof claim 1, wherein the program instructions stored on thenon-transitory computer-readable medium that, when executed by the atleast one processor, cause the first playback device to performfunctions comprising causing the second playback device to proceed withthe extraction of the sound data comprise program instructions stored onthe non-transitory computer-readable medium that, when executed by theat least one processor, cause the first playback device to performfunctions comprising: instructing the second playback device to performthe extraction of the sound data.
 5. The first playback device of claim1, wherein the extraction of the sound data involves transmission of thesound data to the network-based system.
 6. The first playback device ofclaim 1, further comprising program instructions stored on thenon-transitory computer-readable medium that, when executed by the atleast one processor, cause the first playback device to performfunctions comprising: receiving the sound data from the second playbackdevice via the network interface; and transmitting the received sounddata to the network-based system via the network interface.
 7. The firstplayback device of claim 1, wherein the sound is a first sound, thesound data is first sound data, and the indication is a firstindication, the first playback device further comprising programinstructions stored on the non-transitory computer-readable medium that,when executed by the at least one processor, cause the first playbackdevice to perform functions comprising: detecting a second sound via theat least one microphone; identifying the wake word based on the secondsound as detected by the first playback device; receiving, via thenetwork interface, a second indication that the second playback devicehas also detected the second sound and identified the wake word based onthe second sound as detected by the second playback device; afterreceiving the second indication, evaluating which of the first andsecond playback devices is to extract second sound data representing thesecond sound and thereby determining that the extraction of the secondsound data is to be performed by the first playback device over thesecond playback device; beginning to perform the extraction of thesecond sound data; and thereafter ceasing the extraction of the secondsound data in response to receiving a third indication that thenetwork-based system has selected a third playback device to performextraction of the second sound data.
 8. The first playback device ofclaim 7, wherein the first playback device and the second playbackdevice are members of a bonded set, and wherein the third playbackdevice is not a member of the bonded set.
 9. The first playback deviceof claim 1, wherein the VAS response data comprises at least one of (a)a data representation of the given VAS response or (b) an identifier ofthe given VAS response.
 10. A tangible, non-transitory,computer-readable medium having program instructions stored thereon thatare executable by one or more processors to cause a first playbackdevice of a local playback network to: detect sound via at least onemicrophone of the first playback device; identify a wake word based onthe sound as detected by the first playback device; receive, via anetwork interface of the first playback device, an indication that asecond playback device of the local playback network has also detectedthe sound and identified the wake word based on the sound as detected bythe second playback device; after receiving the indication, evaluatewhich of the first and second playback devices is to extract sound datarepresenting the sound and thereby determine that the extraction of thesound data is to be performed by the second playback device over thefirst playback device; based on determining that the extraction of thesound data is to be performed by the second playback device over thefirst playback device, (i) cause the second playback device to proceedwith extraction of the sound data and (ii) forego extraction of thesound data at the first playback device; receive, via the networkinterface from a network-based system that is configured to evaluatesound data for voice input and determine a corresponding VAS (VoiceAssistant Service) response, VAS response data that is indicative of agiven VAS response corresponding to a given voice input identified inthe sound data extracted by the second playback device; and based on theVAS response data, output the given VAS response via an audio outputinterface of the first playback device.
 11. The tangible,non-transitory, computer-readable medium of claim 10, wherein theprogram instructions that cause the first playback device to identifythe wake word based on the sound as detected by the first playbackdevice comprise program instructions that are executable to cause thefirst playback device to: trigger the first playback device to determinea first feature of the sound as detected by the first playback device,wherein the indication that the second playback device has also detectedthe sound and identified the wake word based on the sound as detected bythe second playback device comprises an indication of a second featureof the sound as detected by the second playback device, and wherein theprogram instructions that cause the first playback device to evaluatewhich of the first and second playback devices is to extract the sounddata comprise program instructions that are executable to cause thefirst playback device to compare the first feature to the secondfeature.
 12. The tangible, non-transitory, computer-readable medium ofclaim 11, wherein the first feature comprises a first signal-to-noiseratio of the sound as detected by the first playback device, and whereinthe second feature comprises a second signal-to-noise ratio of the soundas detected by the second playback device.
 13. The tangible,non-transitory, computer-readable medium of claim 10, wherein theprogram instructions stored on the tangible, non-transitory,computer-readable medium that, when executed by the one or moreprocessors, cause the first playback device to cause the second playbackdevice to proceed with the extraction of the sound data comprise programinstructions stored on the tangible, non-transitory, computer-readablemedium that, when executed by the one or more processors, cause thefirst playback device to: instruct the second playback device to performthe extraction of the sound data.
 14. The tangible, non-transitory,computer-readable medium of claim 10, wherein the extraction of thesound data involves transmission of the sound data to the network-basedsystem.
 15. The tangible, non-transitory, computer-readable medium ofclaim 10, further comprising program instructions stored on thenon-transitory computer-readable medium that, when executed by the oneor more processors, cause the first playback device to: receive thesound data from the second playback device via the network interface;and transmit the received sound data to the network-based system via thenetwork interface.
 16. A method implemented by a first playback deviceof a local playback network, the method comprising: detecting sound viaat least one microphone; identifying a wake word based on the sound asdetected by the first playback device; receiving, via a networkinterface, an indication that a second playback device of the localplayback network has also detected the sound and identified the wakeword based on the sound as detected by the second playback device; afterreceiving the indication, evaluating which of the first and secondplayback devices is to extract sound data representing the sound andthereby determining that the extraction of the sound data is to beperformed by the second playback device over the first playback device;based on determining that the extraction of the sound data is to beperformed by the second playback device over the first playback device,(i) causing the second playback device to proceed with extraction of thesound data and (ii) foregoing extraction of the sound data at the firstplayback device; receiving, via the network interface from anetwork-based system that is configured to evaluate sound data for voiceinput and determine a corresponding VAS response, VAS response data thatis indicative of a given VAS (Voice Assistant Service) responsecorresponding to a given voice input identified in the sound dataextracted by the second playback device; and based on the VAS responsedata, outputting the given VAS response via an audio output interface ofthe first playback device.
 17. The method of claim 16, whereinidentifying the wake word based on the sound as detected by the firstplayback device triggers the first playback device to determine a firstfeature of the sound as detected by the first playback device, whereinthe indication that the second playback device has also detected thesound and identified the wake word based on the sound as detected by thesecond playback device comprises an indication of a second feature ofthe sound as detected by the second playback device, and whereinevaluating which of the first and second playback devices is to extractthe sound data comprises comparing the first feature to the secondfeature.
 18. The method of claim 17, wherein the first feature comprisesa first signal-to-noise ratio of the sound as detected by the firstplayback device, and wherein the second feature comprises a secondsignal-to-noise ratio of the sound as detected by the second playbackdevice.
 19. The method of claim 16, wherein causing the second playbackdevice to proceed with the extraction of the sound data comprises:instructing the second playback device to perform the extraction of thesound data.
 20. The method of claim 16, wherein the extraction of thesound data involves transmission of the sound data to the network-basedsystem.